From: Lennart Borgman <lennart.borgman@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stephen.berman@gmx.net, 6192@debbugs.gnu.org
Subject: bug#6192: 24.0.50; eldoc-mode: unexpected recentering
Date: Mon, 17 May 2010 20:49:09 +0200 [thread overview]
Message-ID: <AANLkTimQ2oikHEM9jgXpTTIN6FAtdAchhVR1QbTZMDDW@mail.gmail.com> (raw)
In-Reply-To: <83eihabcuo.fsf@gnu.org>
On Mon, May 17, 2010 at 8:30 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>>
>> Would it be possible to try 1 line scrolling first, then 2 etc?
>
> Maybe we could, but that would be slow, I think. Don't forget that
> there could be more than one window affected by resizing. And since
> redisplay in general works on each window independently, tieing
> together redispay of the echo area and the windows above the mode line
> would be a complication. Is it really worth that?
Maybe not. Here is another suggestion:
- We could by default show messages truncated. Then we could have a an
idle timer that after maybe 2 second showed the message wrapped.
That would stop the annoying jumping caused by messages we still do
not have a chance to see in the echo area because they are overwritten
by later message (often leaving the lower line blank in the echo
area).
> Also, note that scrolling only by the minimum amount will cause
> annoying jumpy display if some command repeatedly displays messages of
> different length in the echo area.
The above suggestion would take care of that too.
> Recentering once avoids that to a
> large degree, because it more often than not will scroll just once.
Recentering go away! ;-)
> In general, my advice to people who are annoyed by recentering to set
> resize-mini-windows to nil (among other things).
Maybe that is enough, but it could be combined with my suggestion above.
> But if someone wants to work on a redisplay optimization that would
> favor such scrolling, feel free.
next prev parent reply other threads:[~2010-05-17 18:49 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 17:11 bug#6192: 24.0.50; eldoc-mode: unexpected recentering Stephen Berman
2010-05-14 17:49 ` Eli Zaretskii
2010-05-14 18:07 ` Stephen Berman
2010-05-14 21:05 ` Eli Zaretskii
2010-05-14 21:44 ` Stephen Berman
2010-05-15 6:36 ` Eli Zaretskii
2010-05-15 15:40 ` Stephen Berman
2010-05-15 16:44 ` Eli Zaretskii
2010-05-15 17:25 ` Stephen Berman
2010-05-15 17:33 ` Eli Zaretskii
2010-05-15 21:54 ` Stephen Berman
2010-05-15 22:52 ` martin rudalics
2010-05-16 3:07 ` Eli Zaretskii
2010-05-16 8:18 ` martin rudalics
2010-05-16 17:14 ` Eli Zaretskii
2010-05-15 16:53 ` martin rudalics
2010-05-15 17:26 ` Stephen Berman
2010-05-15 19:02 ` martin rudalics
2010-05-15 20:22 ` Eli Zaretskii
2010-05-15 20:47 ` martin rudalics
2010-05-15 21:04 ` Juanma Barranquero
2010-05-15 22:51 ` martin rudalics
2010-05-15 21:14 ` Eli Zaretskii
2010-05-15 22:52 ` martin rudalics
2010-05-15 21:54 ` Stephen Berman
2010-05-15 22:53 ` martin rudalics
2010-05-16 8:17 ` martin rudalics
2010-05-16 10:45 ` Stephen Berman
2010-05-16 12:35 ` martin rudalics
2010-05-16 13:07 ` Stephen Berman
2010-05-16 18:50 ` martin rudalics
2010-05-16 19:48 ` Stephen Berman
2010-05-17 9:06 ` martin rudalics
2010-05-17 9:47 ` Stephen Berman
2010-05-17 10:21 ` Juanma Barranquero
2010-05-17 10:31 ` Stephen Berman
2010-05-17 14:08 ` Stefan Monnier
2010-05-17 14:43 ` Lennart Borgman
2010-05-17 16:23 ` Juanma Barranquero
2010-05-17 16:33 ` Lennart Borgman
2010-05-17 16:39 ` Juanma Barranquero
2010-05-17 17:53 ` Eli Zaretskii
2010-05-17 18:02 ` Lennart Borgman
2010-05-17 18:30 ` Eli Zaretskii
2010-05-17 18:49 ` Lennart Borgman [this message]
2010-05-17 19:27 ` Lennart Borgman
2010-05-17 19:55 ` Stefan Monnier
2010-05-14 21:05 ` Eli Zaretskii
2022-05-05 12:20 ` bug#14520: 24.3; minibuffer resizes when message contains bold or italic text Lars Ingebrigtsen
2022-05-05 12:50 ` Stephen Berman
2022-05-05 13:07 ` Lars Ingebrigtsen
2022-05-05 16:25 ` bug#14520: bug#6192: " 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=AANLkTimQ2oikHEM9jgXpTTIN6FAtdAchhVR1QbTZMDDW@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=6192@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stephen.berman@gmx.net \
/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.