GNU bug report logs - #62621
29.0.60; uniquify can't make buffers unique based on things other than filename

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: sbaugh <at> catern.com, sbaugh <at> janestreet.com
Cc: 62621 <at> debbugs.gnu.org
Subject: Re: bug#62621: 29.0.60;
 uniquify can't make buffers unique based on things other than filename
Date: Sat, 15 Jul 2023 09:20:41 +0300

> Cc: sbaugh <at> janestreet.com, 62621 <at> debbugs.gnu.org
> Date: Sat, 15 Jul 2023 08:42:06 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> 
> > From: sbaugh <at> catern.com
> > Date: Fri, 14 Jul 2023 19:15:50 +0000 (UTC)
> > Cc: Spencer Baugh <sbaugh <at> janestreet.com>, 62621 <at> debbugs.gnu.org
> > 
> > Yes.  But how would you implement it so that setting the defcustom to
> > 'project causes the project-uniquify-dirname-transform logic to be used
> > by uniquify.el, without mentioning project-uniquify-dirname-transform or
> > other project functions in uniquify.el?
> 
> You can use autoloading, for example.  Or explicitly
> (require 'project) when that value is seen.  Or any
> number of other solutions we have for such situations.

Or even add a setter to this new defcustom which would set the
uniquify variable to a project-specific function, and you already had
that situation solved, right?

IOW, we have a lot of possible solutions for this kind of problems,
just select one of them.

Previous Next

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