From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 58193@debbugs.gnu.org, paaguti@gmail.com
Subject: bug#58193: 29.0.50; Screen flickers on with-locale-environment
Date: Fri, 30 Sep 2022 21:34:43 +0300 [thread overview]
Message-ID: <83leq0d83g.fsf@gnu.org> (raw)
In-Reply-To: <87ill44v2o.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 30 Sep 2022 19:43:11 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: paaguti@gmail.com, 58193@debbugs.gnu.org
> Date: Fri, 30 Sep 2022 19:43:11 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > IMO, that assumes to much knowledge on the part of the caller. I'd
> > prefer a variable that would tell the macro that the body does include
> > display.
>
> It's a macro that changes the locale. It doesn't say anything about
> doing redisplay at all, so anybody that wants to do redisplay (for
> whatever reason) will use the normal ways of doing that.
>
> I.e., there's no particular knowledge needed.
Many Lisp programmers don't realize what the macro does, in enough
detail to understand that it might affect the display. Suppressing
redrawing of the frame by default is IMO the wrong default: the
flicker in case redrawing wasn't needed is just an annoyance, whereas
failure to redraw when it is needed is a much more serious problem.
So if we want to make the caller responsible for whether the frame
should be redrawn, the default should to redraw it, and callers that
want to avoid that would need to take some measures to that end.
Which is the opposite of what we have now.
next prev parent reply other threads:[~2022-09-30 18:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 13:05 bug#58193: 29.0.50; Screen flickers on with-locale-environment Pedro Andres Aranda Gutierrez
2022-09-30 13:50 ` Eli Zaretskii
2022-09-30 14:14 ` Lars Ingebrigtsen
2022-09-30 15:43 ` Pedro Andres Aranda Gutierrez
2022-09-30 16:31 ` Lars Ingebrigtsen
2022-10-01 7:26 ` Pedro Andres Aranda Gutierrez
2022-10-01 9:57 ` Lars Ingebrigtsen
2022-09-30 17:31 ` Eli Zaretskii
2022-09-30 17:34 ` Lars Ingebrigtsen
2022-09-30 17:40 ` Eli Zaretskii
2022-09-30 17:43 ` Lars Ingebrigtsen
2022-09-30 18:34 ` Eli Zaretskii [this message]
2022-10-01 6:14 ` Pedro Andres Aranda Gutierrez
2022-10-01 7:10 ` Eli Zaretskii
2022-10-01 7:23 ` Pedro Andres Aranda Gutierrez
2022-10-01 7:33 ` Eli Zaretskii
2022-10-01 8:19 ` Pedro Andres Aranda Gutierrez
2022-10-01 9:10 ` Eli Zaretskii
2022-10-01 10:46 ` Pedro Andres Aranda Gutierrez
2022-10-01 12:05 ` Lars Ingebrigtsen
2022-10-01 13:33 ` Pedro Andres Aranda Gutierrez
2022-10-02 11:58 ` Lars Ingebrigtsen
2022-10-03 5:37 ` Pedro Andres Aranda Gutierrez
2022-10-03 9:03 ` Lars Ingebrigtsen
2022-10-03 16:38 ` Eli Zaretskii
2022-10-03 16:47 ` Pedro Andres Aranda Gutierrez
2022-10-03 17:30 ` Eli Zaretskii
2022-10-04 6:10 ` Pedro Andres Aranda Gutierrez
2022-10-01 9:56 ` Lars Ingebrigtsen
2022-10-01 9:57 ` Lars Ingebrigtsen
2022-10-01 10:01 ` Eli Zaretskii
2022-10-01 10:12 ` Pedro Andres Aranda Gutierrez
2022-10-02 11:57 ` Lars Ingebrigtsen
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=83leq0d83g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58193@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=paaguti@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 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).