From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [Emacs-diffs] master 29c360e: Ensure redisplay after "C-x C-e"
Date: Fri, 06 Nov 2015 09:18:41 -0500 [thread overview]
Message-ID: <jwvbnb7gqvz.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <E1ZudLX-0004XR-KP@vcs.savannah.gnu.org> (Eli Zaretskii's message of "Fri, 06 Nov 2015 09:30:11 +0000")
> + ;; If we are going to display the result in the echo area, force
> + ;; a more thorough redisplay, in case the sexp we evaluated
> + ;; changes something that should affect the display of the
> + ;; current window. Otherwise, Emacs might decide that only the
> + ;; echo area needs to be redisplayed.
> + (if (eq standard-output t)
> + (force-mode-line-update 'all)))))
What does this have to do with elisp--eval-last-sexp?
Some changes aren't immediately reflected on screen (e.g. toggling
a minor-mode variable) unless one explicitly requests a redisplay or
call force-mode-line-update.
That's always been the case for setting line-spacing. Sometimes you get
lucky, and after setting line-spacing the change is immediately
reflected on screen because you happen to make some other change at the
same time, but it's just wrong to rely on that.
So I think the above change is a bad idea. If we want to "fix it
right", then we should look for ways to automatically react to changes
to line-spacing, rather than doing (force-mode-line-update 'all) in
elisp--eval-last-sexp, which only catches this problem when it goes
through elisp--eval-last-sexp, and which causes unnecessary redisplay
work in the 99.9% of the cases where elisp--eval-last-sexp does
something else.
Stefan
next parent reply other threads:[~2015-11-06 14:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151106093011.17282.48378@vcs.savannah.gnu.org>
[not found] ` <E1ZudLX-0004XR-KP@vcs.savannah.gnu.org>
2015-11-06 14:18 ` Stefan Monnier [this message]
2015-11-06 14:31 ` [Emacs-diffs] master 29c360e: Ensure redisplay after "C-x C-e" Eli Zaretskii
2015-11-06 14:53 ` Artur Malabarba
2015-11-06 15:30 ` Eli Zaretskii
2015-11-06 16:11 ` Artur Malabarba
2015-11-06 16:30 ` Eli Zaretskii
2015-11-06 19:25 ` Eli Zaretskii
2015-11-07 23:41 ` Stefan Monnier
2015-11-08 3:36 ` Eli Zaretskii
2015-11-08 9:23 ` David Kastrup
2015-11-08 15:54 ` Eli Zaretskii
2015-11-08 15:55 ` Drew Adams
2015-11-08 16:07 ` David Kastrup
2015-11-08 22:25 ` Stefan Monnier
2015-11-09 3:32 ` Eli Zaretskii
2015-11-06 15:33 ` Stefan Monnier
2015-11-06 15:30 ` Stefan Monnier
2015-11-06 15:47 ` Eli Zaretskii
2015-11-06 15:54 ` Eli Zaretskii
2015-11-06 21:47 ` Stefan Monnier
2015-11-07 9:07 ` 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=jwvbnb7gqvz.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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.