unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: 22637@debbugs.gnu.org
Subject: bug#22637: 25.1.50; `mode-line` face `:height` incompatible with `scroll-conservatively 101`.
Date: Fri, 12 Feb 2016 10:17:18 +0200	[thread overview]
Message-ID: <831t8i8hrl.fsf@gnu.org> (raw)
In-Reply-To: <m21t8ioevq.wl%esq@lawlist.com> (message from Keith David Bershatsky on Thu, 11 Feb 2016 18:12:57 -0800)

> Date: Thu, 11 Feb 2016 18:12:57 -0800
> From: Keith David Bershatsky <esq@lawlist.com>
> 
> Setting the `:height` property of the `mode-line` face to 140, and `scroll-conservatively 101`, prevent redisplay from making point fully visible following a large yank of text.

I cannot reproduce this.  I tried some large yanks, including all of
xdisp.c, and the cursor stayed fully visible.

IME, it is sometimes required to make small changes to the default
font, like enlarge it by 1 or 2 pixels, to reproduce problems seen on
other platforms.  I will do that if needed, but please provide a full
recipe, including the text you yanked, and the precise keystrokes used
to yank it: I'd like to be sure I do all the same gestures you did,
before I start playing with font sizes.

> As a suggestion / feature, please consider adding a GLYPH_DEBUG message to indicate when a function from the `timer-idle-list` has triggered a redisplay.

We already have that, albeit in a subtle way: when that happens, you
should see this on stderr:

  redisplay_preserve_echo_area (8)

That "8" part says redisplay_preserve_echo_area was invoked by the
function that ran timers just before that.  You should be able to see
the code which produces that in detect_input_pending_run_timers,
around line 9836 in keyboard.c.

Thanks.





  reply	other threads:[~2016-02-12  8:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12  2:12 bug#22637: 25.1.50; `mode-line` face `:height` incompatible with `scroll-conservatively 101` Keith David Bershatsky
2016-02-12  8:17 ` Eli Zaretskii [this message]
2016-02-12 16:17 ` Keith David Bershatsky
2016-02-12 19:40   ` Eli Zaretskii
2016-02-14  3:40 ` Keith David Bershatsky
2016-02-14  6:05   ` Eli Zaretskii
2016-02-14  7:55 ` Keith David Bershatsky
2016-02-14 19:26   ` Eli Zaretskii
2016-02-16  2:00 ` Keith David Bershatsky
2016-02-16  2:51 ` Keith David Bershatsky
2016-02-16 15:51   ` Eli Zaretskii
2022-02-10  8:09     ` Lars Ingebrigtsen
2022-02-10 12:33       ` 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

  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=831t8i8hrl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22637@debbugs.gnu.org \
    --cc=esq@lawlist.com \
    /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).