From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Cc: gerd.moellmann@gmail.com, monnier@iro.umontreal.ca
Subject: Re: Removing redisplay-dont-pause
Date: Sat, 30 Nov 2024 11:58:03 +0200 [thread overview]
Message-ID: <86v7w582ms.fsf@gnu.org> (raw)
In-Reply-To: <86ed3awd16.fsf@gnu.org> (message from Eli Zaretskii on Sun, 17 Nov 2024 09:11:01 +0200)
Ping! Any opinions? Or should we install Gerd's changes?
> Date: Sun, 17 Nov 2024 09:11:01 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca
>
> > From: Gerd Möllmann <gerd.moellmann@gmail.com>
> > Cc: Stefan Monnier <monnier@iro.umontreal.ca>
> > Date: Sun, 17 Nov 2024 06:43:06 +0100
> >
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> > >> branch: scratch/tty-child-frames
> > >> commit f62d70f52f4f6b7ed158d618bf790df21f171172
> > >> Author: Gerd Möllmann <gerd@gnu.org>
> > >> Commit: Gerd Möllmann <gerd@gnu.org>
> > >>
> > >> Don't pause display for pending input
> > >>
> > >> * src/dispnew.c: Remove display_completed, redisplay_dont_pause,
> > >> redisplay-dont-pause was declared obsolete in Emacs 24. Remove anything
> > >> checking pending input, change function signatures accordingly, and so
> > >> on.
> > >>
> > >> * src/keyboard.c (read_char): Don't use redisplay_dont_pause.
> > >> * src/minibuf.c (read_minibuf): Use new function signatures.
> > >> * src/xdisp.c: Don't check display_completed. Use new API.
> > >>
> > >> * lisp/subr.el (redisplay-dont-pause): Remove declaration.
> > >
> > > I don't think this kind of change is appropriate. Feature branches
> > > should not add/remove features not directly related to the feature
> > > being developed on the branch. If we want to remove
> > > redisplay-dont-pause from Emacs (and I'm not yet sure we do), it
> > > should be discussed on emacs-devel or in a dedicated bug report, not
> > > silently installed on the branch.
> >
> > I guess not many know what this is about, so what is this about?
> >
> > One feature of the old redisplay was that it stopped updating the
> > display when it detected that input was pending, so that it could
> > process that input ASAP.
> >
> > I kept that feature in my redisplay. As a debugging aid, I added
> > redisplay-dont-pause with which I could turn this feature on and off,
> > because pausing the display lead to a lot subtle and difficult to debug
> > bugs.
> >
> > ISTR that setting redisplay-dont-pause to t became sort of a secret
> > semi-popular hack. Hyrum's Law in action, I guess. And 13 years ago or
> > so, the default of redisplay-dont-pause was changed to t by Eli.
> >
> > 10 years ago, Stefan Monnier explained the why
> >
> > + /* Contrary to expectations, a value of "false" can be detrimental to
> > + responsiveness since aborting a redisplay throws away some of the
> > + work already performed. It's usually more efficient (and gives
> > + more prompt feedback to the user) to let the redisplay terminate,
> > + and just completely skip the next command's redisplay (which is
> > + done regardless of this setting if there's pending input at the
> > + beginning of the next redisplay). */
> > + redisplay_dont_pause = true;
> >
> > And finally, Stefan also
> >
> > (make-obsolete-variable 'redisplay-dont-pause nil "24.5")
> >
> > and removed it from the docs.
> >
> > I've removed that pausing feature in my fork and thought I'd bring that
> > to master via scratch/tty-child-frames, but apparently that's
> > controversial for some reason I don't understand, and I reverted that.
> > And so, here we are.
>
> Thanks for the summary.
>
> So what do people think about removing this variable (and the code
> supporting it) from Emacs? In particular, does anyone use that
> variable in a non-default nil value?
>
>
next prev parent reply other threads:[~2024-11-30 9:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 5:43 Removing redisplay-dont-pause Gerd Möllmann
2024-11-17 7:11 ` Eli Zaretskii
2024-11-30 9:58 ` Eli Zaretskii [this message]
2024-11-30 18:56 ` Stefan Monnier
2024-12-01 9:46 ` Mattias Engdegård
2024-12-01 10:08 ` Eli Zaretskii
2024-12-01 10:43 ` Ihor Radchenko
2024-12-01 14:40 ` Eli Zaretskii
2024-12-01 14:49 ` Ihor Radchenko
2024-12-01 15:20 ` Eli Zaretskii
2024-12-02 2:38 ` Stefan Monnier
2024-12-02 4:18 ` Gerd Möllmann
2024-12-02 23:50 ` Stefan Monnier
2024-12-03 4:55 ` Gerd Möllmann
2024-12-14 15:34 ` Ihor Radchenko
2024-12-01 15:28 ` Gerd Möllmann
2024-12-01 15:57 ` Eli Zaretskii
2024-12-09 2:19 ` Stefan Kangas
2024-12-15 1:01 ` Stefan Kangas
2024-12-15 2:46 ` Gerd Möllmann
2024-12-15 7:51 ` Eli Zaretskii
2024-12-19 10:07 ` Gerd Möllmann
2024-12-19 11:15 ` Vincenzo Pupillo
2024-12-19 11:17 ` Gerd Möllmann
2024-12-19 11:46 ` Vincenzo Pupillo
2024-12-15 7:36 ` 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=86v7w582ms.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.