From: Matthias Meulien <orontee@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Name of buffers created by project-shell
Date: Sat, 08 May 2021 19:09:05 +0200 [thread overview]
Message-ID: <87sg2xrw3y.fsf@gmail.com> (raw)
In-Reply-To: <e368df30-68d1-80d9-70a2-3b42ce5185bd@yandex.ru> (Dmitry Gutov's message of "Sun, 21 Mar 2021 21:44:19 +0200")
Hi Dmitry,
Sorry for the late reply, I didn't found much time to work on this until
now.
> Actually, it didn't occur for vc-dir buffers. So it's arguably a bug
> in my code.
>
> Attaching the updated patch which fixes that particular problem,
> though I'm a little more suspicious of some of uniquify's choices now.
I agree that uniquify way of handling buffers not visiting files is
fragile...
> In particular, this code depends on list-buffers-directory being set
> to a value in particular format which is very non-obvious from this
> variable's docstring.
Yes, and shell-mode already sets list-buffers-directory to the default
directory which is not the
(expand-file-name "*shell*" default-directory)
that uniquify would expect (and is overwritten by your patch).
> And to have uniquify work similarly with buffers created by M-x shell
> and M-x eshell as well, these commands need similar changes (we can't
> really depend on them in project.el because it's an ELPA Core
> package), as well as shell-mode and eshell-mode being listed in
> uniquify-list-buffers-directory-modes.
When shell minor mode dirtrack-mode is enabled (the default), the value
of list-buffers-directory is updated when cd, pushd, popd, etc. are
issued; It will thus interfere if uniquify has to rerationalize the
buffer name...
I saw in commit 1c3a86e7fc2 that project-prefixed-buffer-name has been
introduced which I understand as "forgot of uniquify since it doesn't
handle buffer not visiting files properly". I have some time to work on
improving the uniquify situation but can you confirm there's still
interest for this?
My rough plan is to change uniquify-list-buffers-directory-modes to be a
mapping from major modes to functions that, given a buffer, returns the
buffer proposed name and a directory. This would remove the use of
list-buffers-directory in uniquify and gives the opportunity for each
major mode to provide its convenience function based on
current-directory or project-root.
The default won't be to add shell-mode and eshell-mode to this new
uniquify-list-buffers-directory-modes mapping (to avoid breaking current
behavior) but do it locally when shell or eshell are called from
project.el. Is this dependency acceptable?
--
Matthias
next prev parent reply other threads:[~2021-05-08 17:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 21:18 Name of buffers created by project-shell Matthias Meulien
2021-03-04 3:21 ` Dmitry Gutov
2021-03-04 4:03 ` Stefan Monnier
2021-03-04 17:50 ` Juri Linkov
2021-03-05 14:22 ` Dmitry Gutov
2021-03-14 13:46 ` Matthias Meulien
2021-03-15 0:41 ` Dmitry Gutov
2021-03-15 13:05 ` Matthias Meulien
2021-03-21 19:44 ` Dmitry Gutov
2021-03-23 20:08 ` Matthias Meulien
2021-03-24 20:12 ` Juri Linkov
2021-03-24 20:47 ` Dmitry Gutov
2021-05-08 17:09 ` Matthias Meulien [this message]
2021-05-10 0:08 ` Dmitry Gutov
2021-03-14 13:56 ` Matthias Meulien
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=87sg2xrw3y.fsf@gmail.com \
--to=orontee@gmail.com \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
/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).