From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: gnus-correct-length vs. string-width
Date: Sat, 29 Dec 2001 00:24:39 +0100 [thread overview]
Message-ID: <m3666rorm0.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <iluadw3mf85.fsf@extundo.com>
Simon Josefsson <jas@extundo.com> writes:
> When I try the examples from the original thread
> (<87itf461hj.fsf@inanna.rimspace.net> etc) `string-width' works fine.
> (format "%-10s" ...) with wide characters still behaves differently
> between Emacs and XEmacs though, but that shouldn't matter.
It seems to work correctly on Emacs 20, 21 and XEmacs 21, so I think
we should probably ditch `gnus-correct-length' and related functions
like `gnus-char-width'.
Or, at the very least, have gnus-ems.el just check whether
`string-width' gives reasonable results, and defalias according to
that.
Unless somebody has a good reason for why we shouldn't do that...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2001-12-28 23:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-28 14:26 Jesper Harder
2001-12-28 17:22 ` Simon Josefsson
2001-12-28 23:24 ` Lars Magne Ingebrigtsen [this message]
2002-01-05 7:00 ` Daniel Pittman
2002-01-05 16:08 ` Lars Magne Ingebrigtsen
2002-01-06 11:25 ` Daniel Pittman
2001-12-30 1:32 ` Jesper Harder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3666rorm0.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).