unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 58193@debbugs.gnu.org
Subject: bug#58193: 29.0.50; Screen flickers on with-locale-environment
Date: Sat, 1 Oct 2022 10:19:19 +0200	[thread overview]
Message-ID: <FF990BD2-D894-4149-A175-10A865DD70B7@gmail.com> (raw)
In-Reply-To: <83wn9katho.fsf@gnu.org>

Eli
This is just an example. But there are other… currency being one of them.
Best /PA

Enviado desde mi iPhone

> El 1 oct 2022, a las 9:33, Eli Zaretskii <eliz@gnu.org> escribió:
> 
> 
>> 
>> From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
>> Date: Sat, 1 Oct 2022 09:23:12 +0200
>> Cc: larsi@gnus.org, 58193@debbugs.gnu.org
>> 
>>> Maybe we should leave this macro as-is because of the legacy and work towards something in the
>> line of the
>>> cl-setlocale function in Common LISP.
>> 
>> Common Lisp is just a programming language, it is not a display
>> editor.  In Emacs, certain operations that affect the display should
>> be immediately reflected on display.
>> 
>> So, one implication of my question is whether all operations that need a specific locale to be set need the
>> display redrawn... 
> 
> If all you want is to have time displayed per a certain locale's
> conventions, maybe it's enough to set system-time-locale?  Did you try
> that?  set-locale-environment (which is what with-locale-environment
> uses) does much more than just adjusts the locale's time format.





  reply	other threads:[~2022-10-01  8:19 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 [this message]
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=FF990BD2-D894-4149-A175-10A865DD70B7@gmail.com \
    --to=paaguti@gmail.com \
    --cc=58193@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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 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).