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: Sat, 21 May 2016 19:01:10 +0000 [thread overview]
Message-ID: <20160521190110.GB2987@acm.fritz.box> (raw)
In-Reply-To: <83k2in72de.fsf@gnu.org>
Hello, Eli.
On Sat, May 21, 2016 at 08:22:05PM +0300, Eli Zaretskii wrote:
> > Date: Sat, 21 May 2016 10:47:20 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > emacs -Q
> > C-x b foo.c
> > M-x c-mode
> > Type the following five lines into the buffer:
> > #########################################################################
> > char foo [] = "foo";
> > #define FOO BAR
> > char bar [] = "bar";
> > #########################################################################
> > Move point to just after "BAR" on line 3.
> > C-u C-x =
> > There are now two display bugs evident:
> > 1. The vertical divider between the two windows is missing a piece just
> > after the line " decomposition: (10) ('" in *Help*.
> > 2. In foo.c, the actual text display is out of sync with the text cursor.
> > The text has been scrolled one line up, but the cursor has remained at
> > the same position in the window, apparently at the end of a non-existent
> > line of spaces. The cursor can be freely moved, but is one line out of
> > sync with the displayed text.
> I see this, but I don't understand why you needed the c-mode stuff and
> the text. the same problem happens in a buffer in Fundamental mode
> when you invoke "C-u C-x =" at a newline.
Hmm. Maybe I wanted to take some of the blame. ;-)
> 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.
OK. The next question is is it easy to fix?
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2016-05-21 19:01 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 [this message]
2016-05-21 19:09 ` Eli Zaretskii
2016-05-21 20:35 ` Alan Mackenzie
2016-05-22 9:38 ` Alan Mackenzie
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=20160521190110.GB2987@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).