From: Lars Ingebrigtsen <larsi@gnus.org>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 44023@debbugs.gnu.org
Subject: bug#44023: dired-allow-duplicate-buffers
Date: Mon, 19 Oct 2020 10:11:42 +0200 [thread overview]
Message-ID: <87ft6ahby9.fsf@gnus.org> (raw)
In-Reply-To: <20201018054523.xy5lggg3nft7263u@E15-2016.optimum.net> (Boruch Baum's message of "Sun, 18 Oct 2020 01:45:23 -0400")
Boruch Baum <boruch_baum@gmx.com> writes:
>> > Dired internally (in the very line being modified by my
>> > patch) actively subverts having several buffers visiting the same
>> > directory,
>>
>> What line are you referring to?
>
> - (buffer (dired-find-buffer-nocreate dirname mode))
>
> It's the only line changed in the patch file, at the beginning of
> function dired-internal-noselect.
Ah, yes, it seems like dired is working the same as when visiting a
regular file here. As find-file says:
---
Switch to a buffer visiting file FILENAME,
creating one if none already exists.
---
Dired buffers aren't "visiting" files in the same way that regular files
are, but it tries to keep the same semantics.
So renaming a dired buffer doesn't help at all, because Emacs will
always root out the already-existing buffer that points to that
directory. I wonder whether that's on purpose, or whether it just
happens that way by accident. Or is there a way to rename a dired
buffer so that you can have two of them pointing to the same directory?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-10-19 8:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 19:22 bug#44023: dired-allow-duplicate-buffers Boruch Baum
2020-10-16 5:32 ` Lars Ingebrigtsen
2020-10-16 6:46 ` Boruch Baum
2020-10-16 16:25 ` Lars Ingebrigtsen
2020-10-18 5:45 ` Boruch Baum
2020-10-19 8:11 ` Lars Ingebrigtsen [this message]
2020-10-19 8:38 ` Boruch Baum
2020-11-05 15:38 ` Stefan Monnier
2020-11-05 16:06 ` Stefan Monnier
2020-11-06 10:01 ` Boruch Baum
2020-11-06 14:29 ` Stefan Monnier
2020-11-08 9:51 ` Boruch Baum
2020-11-08 13:50 ` Stefan Monnier
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=87ft6ahby9.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=44023@debbugs.gnu.org \
--cc=boruch_baum@gmx.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.