all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70593@debbugs.gnu.org
Subject: bug#70593: 30.0.50; Dired: buffers of renamed dirs are broken
Date: Sat, 18 May 2024 22:45:00 +0200	[thread overview]
Message-ID: <87a5kmyhmb.fsf@web.de> (raw)
In-Reply-To: <861q6syxzb.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 26 Apr 2024 17:55:52 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> So all we need to do is call expand-file-name on both of them?  Or do
> we need also to call file-truename?

When symlinks are involved it gets really messy.

For example: here is an additional problem I encountered:
`dired-rename-subdir' sometimes doesn't even handle our buffer because
`dired-fun-in-all-buffers', which is built on `dired-buffers-for-dir',
doesn't consider symlinks at all: For `dired-buffers-for-dir' a buffer
that visits some DIR under a different name is simply not visiting DIR.

Other problems are: our buffer could visit a file under a now dead link.
The file renamed could have been moved from behind a link to some
completely unrelated place.  Our buffer could dired a subdirectory of a
renamed directory (this case is currently completely ignored).

I feel a bit lost.  Fixing this would be nice, at least the cases where
this is possible, but it's really complicated and I don't even know the
dired code very well.

Michael.





  parent reply	other threads:[~2024-05-18 20:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26 11:59 bug#70593: 30.0.50; Dired: buffers of renamed dirs are broken Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-26 14:55 ` Eli Zaretskii
2024-04-29 14:42   ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-09 13:46     ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-09 14:05       ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-09 16:30       ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-09 19:27         ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-09 21:20           ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-10 12:56             ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-10 13:08               ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-10 16:52                 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-10 16:51               ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-10 17:02                 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-10 18:32                   ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-17 14:29                     ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 20:45   ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-05-19  5:32     ` Eli Zaretskii
2024-05-21 22:43       ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87a5kmyhmb.fsf@web.de \
    --to=bug-gnu-emacs@gnu.org \
    --cc=70593@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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.