GNU bug report logs - #78890
31.0.50; Messy vc-annotate buffer names

Previous Next

Full log

Message #80 received at 78890 <at> debbugs.gnu.org (full text, mbox):

From: Sean Whitton <spwhitton <at> spwhitton.name>
To: Jim Porter <jporterbugs <at> gmail.com>
Cc: Stephen Berman <stephen.berman <at> gmx.net>,
 Kristoffer Balintona <krisbalintona <at> gmail.com>, 78890 <at> debbugs.gnu.org
Subject: Re: bug#78890: 31.0.50; Messy vc-annotate buffer names
Date: Thu, 26 Jun 2025 19:27:14 +0100

Hello,

On Thu 26 Jun 2025 at 10:13am -07, Jim Porter wrote:

> On 6/26/2025 9:57 AM, Sean Whitton wrote:
>> Well, I was wondering about this.  I was thinking that using the
>> absolute filename was desirable in that case for disambiguation.
>> If file-buffer is non-nil then we already know it will have been
>> uniquified so as to be unambiguous.
>
> I suppose it's just personal preference, but I'd rather the buffer name err on
> the side of brevity, since in an 80-column frame, an absolute file name could
> easily fill up the entire mode line so that the revision identifier is
> off-screen (to say nothing of other mode line elements).

I'm more concerned about an actual clash in buffer names between files
with the same name in different directories.  What do you think about
that?

-- 
Sean Whitton

Previous Next

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