unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58193@debbugs.gnu.org, paaguti@gmail.com
Subject: bug#58193: 29.0.50; Screen flickers on with-locale-environment
Date: Sun, 02 Oct 2022 13:57:58 +0200	[thread overview]
Message-ID: <87pmfae8u1.fsf@gnus.org> (raw)
In-Reply-To: <83pmfbc16b.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 01 Oct 2022 13:01:48 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Fair enough, but if this macro is not intended for BODYs that include
> visual appearance, the restriction should be mentioned in the doc
> string, I think.

It's a macro that sets the locale, evaluates the body, and restores the
previous locale.  I can't for the life of me understand why somebody
would think that it has something to do with the visual appearance of
anything, one way or another.





      parent reply	other threads:[~2022-10-02 11:57 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
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 [this message]

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=87pmfae8u1.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=58193@debbugs.gnu.org \
    --cc=eliz@gnu.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).