From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pedro Andres Aranda Gutierrez Newsgroups: gmane.emacs.bugs Subject: bug#58193: 29.0.50; Screen flickers on with-locale-environment Date: Mon, 3 Oct 2022 07:37:56 +0200 Message-ID: References: <87wn9l3q5i.fsf@gnus.org> <83sfk8db0m.fsf@gnu.org> <87mtag4vhi.fsf@gnus.org> <83mtagdall.fsf@gnu.org> <87ill44v2o.fsf@gnus.org> <83leq0d83g.fsf@gnu.org> <83y1u0auk4.fsf@gnu.org> <83wn9katho.fsf@gnu.org> <87y1tzhhq1.fsf@gnus.org> <87lepye8st.fsf@gnus.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000007ac0d205ea1ac0d4" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2863"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , 58193@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Oct 03 07:40:04 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ofEBP-0000Zs-JQ for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 03 Oct 2022 07:40:03 +0200 Original-Received: from localhost ([::1]:54474 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ofEBN-0000BA-Ce for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 03 Oct 2022 01:40:02 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55366) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofEAR-0000AQ-Hc for bug-gnu-emacs@gnu.org; Mon, 03 Oct 2022 01:39:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49518) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ofEAQ-0000K1-Eo for bug-gnu-emacs@gnu.org; Mon, 03 Oct 2022 01:39:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ofEAQ-0005Fi-0L for bug-gnu-emacs@gnu.org; Mon, 03 Oct 2022 01:39:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Pedro Andres Aranda Gutierrez Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 03 Oct 2022 05:39:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 58193 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 58193-submit@debbugs.gnu.org id=B58193.166477551120153 (code B ref 58193); Mon, 03 Oct 2022 05:39:01 +0000 Original-Received: (at 58193) by debbugs.gnu.org; 3 Oct 2022 05:38:31 +0000 Original-Received: from localhost ([127.0.0.1]:48596 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ofE9v-0005Ez-6N for submit@debbugs.gnu.org; Mon, 03 Oct 2022 01:38:31 -0400 Original-Received: from mail-ed1-f46.google.com ([209.85.208.46]:35620) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ofE9s-0005Ej-VU for 58193@debbugs.gnu.org; Mon, 03 Oct 2022 01:38:29 -0400 Original-Received: by mail-ed1-f46.google.com with SMTP id s2so2463385edd.2 for <58193@debbugs.gnu.org>; Sun, 02 Oct 2022 22:38:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=4hAptahSdPDLO0raZoypaW7tW22tjno0zpd+iYjr468=; b=ai0nm8LWSaUyeMAGZb5+R/tH2Vaius8k9Ee4ziDf20ZjCGJSGH0oynH/RbXBdzzy01 2c/eSkYpnxi4nw5XpD7o8US74UWoW9l67JU2G0nzqf/M7z1tS13r3M7BFmtJtKF/WYZ+ tzoLqUgbvU06ID0AhjabirpSWomngq7EPs/CTbVo2kRRE49mHqk06uIXqOtllxucH10R HWATWTuYdCINqi9iUCnlGu1jhm6JiZN/8MFSkZbZS7nWscz4NRg6ilnwzcjCX5he8UwG 5lBCyMKpizQWLZocZ19f1Pqfp/7Jgkbsex3HKTFeOLB8MP8FCK5nEOMjqZ5jWXAcn9R/ oXNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=4hAptahSdPDLO0raZoypaW7tW22tjno0zpd+iYjr468=; b=RY+Gi5WyPsM4ORBOeZAvw05uz8/VXzGGtONV6jBEVAg6RN82wP6TFDptcLPhwG4vjQ 81tmAMVo6DxMzVcS2v5FrB7ckdBRDU9Bfn0bQRH7wuz9vz2vDct6rNbW4cZYow4tPwHi v68HQxBU3pqK34ojs+1d9kCWCVl8e+QYVouDkDgSzAmPuVSm39Yp1X1XkF0vbWHaucu6 7eR3EIxmswBmtGatikv70sRj9ZjVMA78zsvXLy3CrRMEoMD2qQ78FhaGSoid11Q+fcvS qsN+JsfbxSyPGI+Yn3vVE4XXxM0DVj1xNPIme5nWJFfdQZIX/02vk+ic7n/+GFFYyubA rIvg== X-Gm-Message-State: ACrzQf2sEsaKgA93qJ2ec5pLXHS95eLqlhVTnA0hHSK3v7FNNqjqnC6R M9L25COl0V6h8H+VnD/ip1Av+bcWyL7cxhrn1M8= X-Google-Smtp-Source: AMsMyM4iM8qHDsUTp22Bx5ITDbewGX9Uq2O0L2Xh2nEtXFNdoEJdA5csYoUdRoAR0PdGWZzscn7e/Cb/q8HDXW07asA= X-Received: by 2002:a05:6402:27cf:b0:451:6ccc:4ea0 with SMTP id c15-20020a05640227cf00b004516ccc4ea0mr17504937ede.193.1664775502871; Sun, 02 Oct 2022 22:38:22 -0700 (PDT) In-Reply-To: <87lepye8st.fsf@gnus.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:244283 Archived-At: --0000000000007ac0d205ea1ac0d4 Content-Type: text/plain; charset="UTF-8" Sorry for the "telegram" ;-) I have been working all day yesterday using my functions using 'with-locale-environment' and I didn't experience any flicker. On that side good. On the other hand, I still think that a macro only controlling the system-locale for the time functions may be useful despite, I admit, being somehow redundant. My feeling is that many of the settings changed in with-locale-environment don't need to be changed for format-time-string. Digression: What about adding a third (optional) parameter to format-time-string to set the locale for a specific call? This could be an alternative which might be more-lightweight than with-locale-environment, wouldn't it? Best, /PA On Sun, 2 Oct 2022 at 14:00, Lars Ingebrigtsen wrote: > Pedro Andres Aranda Gutierrez writes: > > > And, at least in my initial test it doesn't > > [...] > > > There should be no flickers with with-locale-environment, either, so it > > seems redundant. > > Does this mean that `with-locale-environment' doesn't flicker the screen > for you any more? I'm not sure how to parse that response... > -- Fragen sind nicht da um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler Headaches with a Juju log: unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run a leader-deposed hook here, but we can't yet --0000000000007ac0d205ea1ac0d4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sorry for the "telegram" ;-)=C2=A0

= I have been working all day yesterday using my functions using 'with-lo= cale-environment' and I didn't experience any flicker.=C2=A0
<= /div>
On that side good. On the other hand, I still think that a macro = only controlling the system-locale for the time functions may be useful des= pite, I admit, being somehow redundant. My feeling is that many of the sett= ings changed in with-locale-environment don't need to be changed for fo= rmat-time-string.=C2=A0

Digression: What about add= ing a third (optional) parameter to format-time-string to set the locale fo= r a specific call? This could be an alternative which might be more-lightwe= ight than with-locale-environment, wouldn't it?

Best, /PA



--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um = gestellt zu werden
Georg Kreisler

Headach= es with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.u= niter.operation we should run a leader-deposed hook here, but we can't = yet

--0000000000007ac0d205ea1ac0d4--