GNU bug report logs - #76980
[PATCH] 'window-state-normalize-buffer-name' variable for `uniquify' buffers

Previous Next

Package: emacs;

Reported by: Ship Mints <shipmints <at> gmail.com>

Date: Wed, 12 Mar 2025 16:47:01 UTC

Severity: normal

Tags: patch

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Ship Mints <shipmints <at> gmail.com>
To: Robert Pluim <rpluim <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 76980 <at> debbugs.gnu.org
Subject: bug#76980: [PATCH] 'window-state-normalize-buffer-name' variable for `uniquify' buffers
Date: Fri, 14 Mar 2025 10:54:05 -0400
[Message part 1 (text/plain, inline)]
On Fri, Mar 14, 2025 at 10:45 AM Robert Pluim <rpluim <at> gmail.com> wrote:

> >>>>> On Fri, 14 Mar 2025 10:26:28 -0400, Ship Mints <shipmints <at> gmail.com>
> said:
>     Ship> ++++
>     Ship> +*** New variable 'window-state-normalize-buffer-name'.
>     Ship> +When bound to non-nil, 'window-state-get' will normalize buffer
> names by
>     Ship> +removing 'uniquify' adornments, otherwise using nominal buffer
> names.
>     Ship> +This helps restore window buffers across Emacs sessions.
>     Ship> +
>
> This sounds like it could be useful as a user option rather than a
> `defvar', no? Or perhaps a buffer-local variable?
>

To me, this is a programmatic concern and only the program understands the
context in which it is called.  In a sense, this is buffer-local equivalent
as uniquify-managed is itself buffer-local.  If this is made global, I
sense there may be window-state-get uses that depend on uniquify names but
since I can't survey the field, I think this would be dangerous.  We can
always promote this to a user option later.
[Message part 2 (text/html, inline)]

This bug report was last modified 55 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.