unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eshel Yaron via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 74091@debbugs.gnu.org
Subject: bug#74091: 31.0.50; string-pixel-width in mode line disables region
Date: Wed, 06 Nov 2024 15:12:24 +0100	[thread overview]
Message-ID: <m15xp08n93.fsf@macbookpro.home> (raw)
In-Reply-To: <86ldxwsf11.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 06 Nov 2024 14:49:46 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Eshel Yaron <me@eshelyaron.com>
>> Cc: 74091@debbugs.gnu.org
>> Date: Wed, 06 Nov 2024 09:01:16 +0100
>> 
>> FYI after spending a bit more time on this issue, I concluded that
>> (kill-all-local-variables t) is inherently problematic: it breaks
>> assumptions that Emacs relies on.  (See bug#73005 for another example.)
>> 
>> It doesn't seem like killing permanent-local variables in the work
>> buffers is necessary ATM, so the fix I'm using is the following:
>
> Can't _any_ variable become permanent-local, by virtue of some Lisp
> program or the user giving it a permanent-local property?
>
> More generally, how do we know that there are no permanent-local
> variables out there that affect layout, and thus affect the results of
> this function?
>
> I believe these considerations were those which led the author to use
> kill-all-local-variables like this: we want to be sure that nothing
> will dupe string-pixel-width into producing unexpected results.

Yes, this reasoning is perfectly understandable.  However, the current
way of killing all permanent-local variables has bad consequences that
that author, naturally, did not expect.  So my suggestion is to avoid
(kill-all-local-variables t) here and elsewhere.

For string-pixel-width specifically, we take care to clear variables
that may affect width calculation.  If other variables may interfere, we
should just clear those too.


Cheers,

Eshel





  reply	other threads:[~2024-11-06 14:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 17:27 bug#74091: 31.0.50; string-pixel-width in mode line disables region Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-30 14:59 ` Eli Zaretskii
2024-10-30 15:26   ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-30 16:01     ` Eli Zaretskii
2024-10-31 11:09       ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-31 11:41         ` Eli Zaretskii
2024-10-31 12:24           ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-31 14:35             ` Eli Zaretskii
2024-11-06  8:01               ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-06 12:49                 ` Eli Zaretskii
2024-11-06 14:12                   ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-11-09 11:13                     ` Eli Zaretskii
2024-11-09 16:26           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-09 16:37             ` Eli Zaretskii
2024-11-09 18:06               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-09 18:14                 ` Eli Zaretskii
2024-11-09 18:35                   ` Eli Zaretskii
2024-11-09 22:11                     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-10  5:50                       ` Eli Zaretskii
2024-11-10  6:50                         ` Eli Zaretskii
2024-11-10 10:42                           ` Eli Zaretskii
2024-11-10 16:46                             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-10 19:17                               ` Eli Zaretskii
2024-11-10 20:19                                 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-11  3:22                                   ` Eli Zaretskii
2024-11-11  6:52                                     ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=m15xp08n93.fsf@macbookpro.home \
    --to=bug-gnu-emacs@gnu.org \
    --cc=74091@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=me@eshelyaron.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).