From: Stefan Monnier <monnier@iro.umontreal.ca>
To: John Shahid <jvshahid@gmail.com>
Cc: 31325@debbugs.gnu.org
Subject: bug#31325: 27.0.50; PROPOSAL: introduce a new function to recenter without redisplaying the frame
Date: Mon, 07 May 2018 21:37:06 -0400 [thread overview]
Message-ID: <jwvsh73vspr.fsf-monnier+bug#31325@gnu.org> (raw)
In-Reply-To: <87po2gkxpi.fsf@gmail.com> (John Shahid's message of "Tue, 01 May 2018 00:48:25 +0000")
> This BUG is a continuation of this help-gnu-emacs mailing list
> thread [1]. As mentioned in the thread, I ran into a terminal flickering
> issue in flycheck which turns out to be caused by `recenter'
> redisplaying the frame when `recenter-redisplay' value is either `t' or
> `tty'. I agree with the arguments in the thread to maintain the backward
> compatible behavior. Instead, I'm proposing one of the following
> alternatives:
Indeed, most/all uses from Elisp shouldn't redisplay.
> 1. introduce a new lisp function for recentering and discourage the use
> of `recenter' from lisp (i.e. declaring it `interactive-only'), or
> 2. add a new `recenter-and-redisplay' and bound it to C-l
> Also, Stefan's suggestion/possible solution:
> 3. adding an argument to `recenter' to control the redisplay behavior
Either of those is OK. The benefit of the 3rd is that it would likely
"magically fix" 99% of the existing uses (I'm thinking of adding an
optional argument which we could call `and-redisplay` which when non-nil
tells recenter to do a redisplay, so all existing Elisp calls would be
implicitly modified not to cause a redisplay).
Stefan
next prev parent reply other threads:[~2018-05-08 1:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 0:48 bug#31325: 27.0.50; PROPOSAL: introduce a new function to recenter without redisplaying the frame John Shahid
2018-05-08 1:37 ` Stefan Monnier [this message]
2018-06-28 13:27 ` John Shahid
2018-06-30 9:45 ` Eli Zaretskii
2018-06-30 20:20 ` John Shahid
2018-07-01 9:05 ` martin rudalics
2018-07-01 13:17 ` John Shahid
2018-07-01 16:22 ` Eli Zaretskii
2018-07-01 16:54 ` John Shahid
2018-07-01 17:03 ` Eli Zaretskii
2018-07-01 17:14 ` Eli Zaretskii
2018-07-01 17:25 ` John Shahid
2018-07-01 20:17 ` Drew Adams
2018-07-01 20:56 ` John Shahid
2018-07-01 23:04 ` Drew Adams
2018-07-02 2:27 ` John Shahid
2018-07-02 15:18 ` Eli Zaretskii
2018-07-01 17:18 ` John Shahid
2018-07-01 18:05 ` Eli Zaretskii
2018-07-01 18:58 ` John Shahid
2018-07-02 15:22 ` Eli Zaretskii
2018-07-02 20:38 ` John Shahid
2018-07-03 8:49 ` Robert Pluim
2018-07-03 16:38 ` John Shahid
2018-07-07 9:09 ` 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='jwvsh73vspr.fsf-monnier+bug#31325@gnu.org' \
--to=monnier@iro.umontreal.ca \
--cc=31325@debbugs.gnu.org \
--cc=jvshahid@gmail.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 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.