From: Visuwesh <visuweshm@gmail.com>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: 74709@debbugs.gnu.org
Subject: bug#74709: [PATCH] Avoid empty unique qualifier in buffer name
Date: Sat, 07 Dec 2024 09:16:08 +0530 [thread overview]
Message-ID: <871pykupdr.fsf@gmail.com> (raw)
In-Reply-To: <87ldwsip87.fsf@ledu-giraud.fr> (Manuel Giraud's message of "Fri, 06 Dec 2024 20:30:16 +0100")
[வெள்ளி டிசம்பர் 06, 2024] Manuel Giraud wrote:
> Visuwesh <visuweshm@gmail.com> writes:
>
>> [வெள்ளி டிசம்பர் 06, 2024] Manuel Giraud via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" wrote:
>>
>>> Tags: patch
>>>
>>> Hi,
>>>
>>> This patch prevents from having an empty unique qualifier in the buffer
>>> name. Maybe this could happen with others file buffer as well but, most
>>> of the time, you could witness it with Dired buffer in homedir. Here is
>>> a recipe:
>>>
>>> - emacs -Q
>>> - C-x d /ssh:somewhere: ;; This buffer is named "~</ssh:somewhere:>"
>>> - C-x d /~/ ;; This buffer is named "~<>"
>>>
>>> With this patch, the last buffer will simply be named "~" instead.
>>
>> I usually have ~/tmp visited in a Dired buffer. Sometimes I also visit
>> /tmp which gets named as "tmp<>". With this patch, /tmp's buffer is
>> named "tmp" instead. This confuses me as I am used to seeing "tmp" for
>> ~/tmp's Dired buffer more often than not. Can we gate this new
>> behaviour behind a user option please?
>
> I don't think that there is more confusion then if you only have /tmp
> opened which will have its buffer named "tmp", no?
Sorry, I meant having /tmp being "tmp" when both ~/tmp and /tmp are open
is confusing for the aforementioned reason.
next prev parent reply other threads:[~2024-12-07 3:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 12:17 bug#74709: [PATCH] Avoid empty unique qualifier in buffer name Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-06 16:16 ` Eli Zaretskii
2024-12-06 16:34 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-06 16:51 ` Eli Zaretskii
2024-12-06 17:17 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-06 17:44 ` Visuwesh
2024-12-06 19:30 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-07 3:46 ` Visuwesh [this message]
2024-12-07 10:04 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-21 9:11 ` 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=871pykupdr.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=74709@debbugs.gnu.org \
--cc=manuel@ledu-giraud.fr \
/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.