From: Eli Zaretskii <eliz@gnu.org>
To: sbaugh@catern.com, sbaugh@janestreet.com
Cc: 62621@debbugs.gnu.org
Subject: 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 [thread overview]
Message-ID: <83bkgdelvq.fsf@gnu.org> (raw)
In-Reply-To: <83pm4teno1.fsf@gnu.org> (message from Eli Zaretskii on Sat, 15 Jul 2023 08:42:06 +0300)
> Cc: sbaugh@janestreet.com, 62621@debbugs.gnu.org
> Date: Sat, 15 Jul 2023 08:42:06 +0300
> From: Eli Zaretskii <eliz@gnu.org>
>
> > From: sbaugh@catern.com
> > Date: Fri, 14 Jul 2023 19:15:50 +0000 (UTC)
> > Cc: Spencer Baugh <sbaugh@janestreet.com>, 62621@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.
next prev parent reply other threads:[~2023-07-15 6:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 17:37 bug#62621: 29.0.60; uniquify can't make buffers unique based on things other than filename Spencer Baugh
2023-04-02 17:57 ` Eli Zaretskii
2023-04-02 21:59 ` Drew Adams
2023-04-02 18:25 ` Juri Linkov
2023-04-14 16:08 ` Spencer Baugh
2023-07-13 22:51 ` sbaugh
2023-07-14 6:29 ` Eli Zaretskii
2023-07-14 11:28 ` sbaugh
2023-07-14 12:01 ` Eli Zaretskii
2023-07-14 12:20 ` Spencer Baugh
2023-07-14 12:29 ` Eli Zaretskii
2023-07-14 12:46 ` Spencer Baugh
2023-07-14 13:51 ` Eli Zaretskii
2023-07-14 14:14 ` Spencer Baugh
2023-07-14 19:10 ` Eli Zaretskii
2023-07-14 19:15 ` sbaugh
2023-07-15 5:42 ` Eli Zaretskii
2023-07-15 6:20 ` Eli Zaretskii [this message]
2023-07-18 0:19 ` Dmitry Gutov
2023-07-18 1:37 ` Dmitry Gutov
2023-07-18 16:03 ` Spencer Baugh
2023-07-19 2:47 ` Dmitry Gutov
2023-07-19 6:56 ` Juri Linkov
2023-07-18 17:51 ` Juri Linkov
2023-07-19 2:24 ` Dmitry Gutov
2023-07-14 16:31 ` Juri Linkov
2023-07-18 0:34 ` Dmitry Gutov
2023-07-18 11:07 ` Eli Zaretskii
2023-07-19 2:22 ` Dmitry Gutov
2023-07-19 12:14 ` Eli Zaretskii
2023-07-19 12:31 ` Spencer Baugh
2023-07-19 13:25 ` Eli Zaretskii
2023-07-21 13:34 ` Spencer Baugh
2023-07-21 14:37 ` Eli Zaretskii
2023-07-22 18:00 ` Spencer Baugh
2023-07-24 19:18 ` Spencer Baugh
2023-07-26 15:18 ` Eli Zaretskii
2023-08-03 8:00 ` Eli Zaretskii
2023-08-03 11:54 ` Spencer Baugh
2023-08-03 14:05 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bkgdelvq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62621@debbugs.gnu.org \
--cc=sbaugh@catern.com \
--cc=sbaugh@janestreet.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.