From: Chong Yidong <cyd@stupidchicken.com>
To: Kenichi Handa <handa@m17n.org>
Cc: 3452@emacsbugs.donarmstrong.com
Subject: bug#3452: 23.0.94; display
Date: Mon, 08 Jun 2009 10:47:38 -0400 [thread overview]
Message-ID: <87prdeaik5.fsf@cyd.mit.edu> (raw)
In-Reply-To: <E1MDdTO-00031x-Np@etlken> (Kenichi Handa's message of "Mon, 08 Jun 2009 20:57:06 +0900")
Kenichi Handa <handa@m17n.org> writes:
>> > It seems xterm, gnome-terminal, GNU/Linux console, and
>> > mlterm treat U+202D as spacing character, but, Konsole
>> > (KDE's terminal) and kterm treats it as non-spacing
>> > character.
>
>> Wasn't gnome-terminal the one that started this bug report?
>
> I don't know exactly. RMS's bug report just says "a 37-line
> Linux terminal".
He means the console on GNU/Linux. I haven't tested there.
The problem I see is on xterm, where the current behavior is very
strange. For example, with your earlier example:
(with-temp-file "~/atemp" (insert #x202d ?a ?\n))
Visit the file with emacs -nw -Q on an xterm and press C-f a few times.
You'll see that the "a" is displayed one glyph to the right of where it
should be. Apprently, the console draws #x202d as two spaces, and this
leads to inconsistent display.
The same problem occurs on gnome-terminal.
next prev parent reply other threads:[~2009-06-08 14:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-07 3:47 bug#3452: 23.0.94; display Chong Yidong
2009-06-07 9:16 ` Eli Zaretskii
2009-06-07 13:56 ` Chong Yidong
2009-06-07 14:30 ` Eli Zaretskii
2009-06-07 20:41 ` Chong Yidong
2009-06-07 22:53 ` Eli Zaretskii
2009-06-08 1:51 ` Kenichi Handa
2009-06-08 4:48 ` Eli Zaretskii
2009-06-08 8:10 ` Kenichi Handa
2009-06-08 8:44 ` Eli Zaretskii
2009-06-08 11:57 ` Kenichi Handa
2009-06-08 14:47 ` Chong Yidong [this message]
2009-06-09 18:00 ` Chong Yidong
2009-06-10 0:35 ` Kenichi Handa
-- strict thread matches above, loose matches on Subject: below --
2009-06-06 2:48 Chong Yidong
2009-06-03 2:53 Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87prdeaik5.fsf@cyd.mit.edu \
--to=cyd@stupidchicken.com \
--cc=3452@emacsbugs.donarmstrong.com \
--cc=handa@m17n.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).