all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nick Helm <nick@tenpoint.co.nz>
Cc: 33363@debbugs.gnu.org
Subject: bug#33363: 26.1; display problem with mode-line turned off on terminal
Date: Sat, 17 Nov 2018 14:44:26 +0200	[thread overview]
Message-ID: <83pnv3ub4l.fsf@gnu.org> (raw)
In-Reply-To: <773094C5-ABD7-4D0D-84D0-1CC60D04CBFB@tenpoint.co.nz> (message from Nick Helm on Tue, 13 Nov 2018 16:40:23 +1300)

> From: Nick Helm <nick@tenpoint.co.nz>
> Date: Tue, 13 Nov 2018 16:40:23 +1300
> 
> Running Emacs in a terminal and setting mode-line-format to nil can 
> cause incorrect display of buffer contents.

Right.  And it's a very old bug.

> emacs -Q -nw
> M-: (setq mode-line-format nil)
> C-x C-f lisp/org/org.el.gz ;for example
> RET RET RET... DEL DEL DEL... ;add and delete white-space
> 
> Note the second-to-last row in the window, which formerly held the
> mode-line, does not display the buffer contents correctly and any buffer
> line that moves through the last row (when back-spacing) appears blank
> further up the window.

The immediate cause of this is that we miscalculate the number of
lines in the window in this case, and then instruct the terminal to
delete the wrong line.  I'm debating how best to fix this; stay tuned.

> I mainly observe this in emacs-lisp-mode and org-mode. The problem 
> doesn't seem to occur when:
> 
> + in fundamental-mode, c-mode or text-mode, or
> + visual-line-mode is active, or
> + the frame contains more than one window (v or h split), or
> + avoiding display of each line (e.g. C-u 10 RET C-u 10 DEL).

The offending code is a redisplay optimization, and is used only under
very specific conditions.  That's why it doesn't rear its ugly head in
many situations.

Thanks.





  reply	other threads:[~2018-11-17 12:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13  3:40 bug#33363: 26.1; display problem with mode-line turned off on terminal Nick Helm
2018-11-17 12:44 ` Eli Zaretskii [this message]
2018-11-19 18:16   ` Eli Zaretskii
2018-11-19 22:00     ` Nick Helm
2018-11-20  3:31       ` Eli Zaretskii

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=83pnv3ub4l.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33363@debbugs.gnu.org \
    --cc=nick@tenpoint.co.nz \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.