From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: gnus-correct-length vs. string-width
Date: Sat, 05 Jan 2002 17:08:30 +0100 [thread overview]
Message-ID: <m3g05kdblt.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <877kqx704t.fsf@inanna.rimspace.net>
Daniel Pittman <daniel@rimspace.net> writes:
> (format "%-10s" ...) differs on character vs byte width between XEmacs
> and GNU Emacs. This means that the "correct" width is lost when doing
> cut operations on wide characters in the summary buffer...
Ah, right; that was it.
But we could alias those functions to the built-in functions on
Emacsen that give us the results we want.
This is under XEmacs:
(string-width (format "%10s" "你好"))
=> 12
And this is under Emacs:
(string-width (format "%10s" "你好"))
=> 10
So how about if we just default `gnus-use-correct-string-widths' to
`(featurep 'xemacs)'?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2002-01-05 16:08 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
2002-01-05 7:00 ` Daniel Pittman
2002-01-05 16:08 ` Lars Magne Ingebrigtsen [this message]
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=m3g05kdblt.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).