From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23594@debbugs.gnu.org
Subject: bug#23594: 25.0.94; Display errors on Linux tty
Date: Sun, 22 May 2016 09:38:13 +0000 [thread overview]
Message-ID: <20160522093813.GA2136@acm.fritz.box> (raw)
In-Reply-To: <83d1of6xe5.fsf@gnu.org>
Hello, Eli.
On Sat, May 21, 2016 at 10:09:38PM +0300, Eli Zaretskii wrote:
> > > This bug exists since we started showing the 'decomposition' of
> > > characters in Emacs 24.1. With LF, we send a literal LF character
> > > to the screen.
That's only half the story. The literal LF doesn't seem to be the
problem. Rather, it's got a 'composition text-property attached to it.
The string we're trying to display is
#(" decomposition: (10) ('\n')\n" 24 25 (composition (0 1 [9 10 9])))
^
|
24
What is this composition trying to do? The [9 10 9] is [\t \n \t].
The whole thing is a result of calling
(char-code-property-description 'decomposition '(10))
Under X-Windows, the same string is displayed, this time successfully.
The call
(inseert #(" decomposition: .... [9 10 9])))
works on X-Windows, the "\n" with the composition property being
displayed as a square box.
> > OK. The next question is is it easy to fix?
> Yes. We should not send control characters to that buffer.
It seems to me there is a bug in the display engine here: the same
string which is displayed successfully in X-Windows goes badly wrong on
a Linux tty.
Comments?
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2016-05-22 9:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 10:47 bug#23594: 25.0.94; Display errors on Linux tty Alan Mackenzie
2016-05-21 17:22 ` Eli Zaretskii
2016-05-21 19:01 ` Alan Mackenzie
2016-05-21 19:09 ` Eli Zaretskii
2016-05-21 20:35 ` Alan Mackenzie
2016-05-22 9:38 ` Alan Mackenzie [this message]
2016-05-22 15:27 ` Eli Zaretskii
2016-05-22 16:16 ` Alan Mackenzie
2016-05-22 16:50 ` Eli Zaretskii
2016-05-22 20:03 ` Alan Mackenzie
2016-05-22 21:12 ` Alan Mackenzie
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=20160522093813.GA2136@acm.fritz.box \
--to=acm@muc.de \
--cc=23594@debbugs.gnu.org \
--cc=eliz@gnu.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).