From: Paul Eggert <eggert@cs.ucla.edu>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: mvar.40k@gmail.com, 11912@debbugs.gnu.org,
Lars Ingebrigtsen <larsi@gnus.org>,
Richard Stallman <rms@gnu.org>
Subject: bug#11912: 24.1; 'M' in Dired on a symlink does not refresh the display
Date: Thu, 26 Aug 2021 09:52:38 -0700 [thread overview]
Message-ID: <e8c9b19b-b59c-8a1e-353a-6180e98b7dbc@cs.ucla.edu> (raw)
In-Reply-To: <875yvsuwo9.fsf@igel.home>
On 8/26/21 7:07 AM, Andreas Schwab wrote:
> But if the dired buffer was created with ls -L, shouldn't M follow
> links?
Yes, in that case I suppose M should do so (and similarly for G, O, T).
This raises the issue of what to do with output like the following from
GNU 'ls' when 'c' is a dangling symlink:
$ ls -lL
ls: cannot access 'c': No such file or directory
total 0
-rw-rw-r-- 1 eggert eggert 0 Aug 26 09:46 b
l????????? ? ? ? ? ? c
However, these are rare cases; typically dired buffers are created
without -L and we need to handle the typical cases better.
next prev parent reply other threads:[~2021-08-26 16:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 16:30 bug#11912: 24.1; 'M' in Dired on a symlink does not refresh the display Eli Zaretskii
2021-08-24 10:23 ` Michalis V.
2021-08-24 15:40 ` Lars Ingebrigtsen
2021-08-24 17:32 ` Paul Eggert
2021-08-25 10:57 ` Lars Ingebrigtsen
2021-08-25 17:59 ` Paul Eggert
2021-08-26 13:52 ` Lars Ingebrigtsen
2021-08-26 3:57 ` Richard Stallman
2021-08-26 13:54 ` Lars Ingebrigtsen
2021-08-26 14:07 ` Andreas Schwab
2021-08-26 16:52 ` Paul Eggert [this message]
2021-08-27 3:30 ` Richard Stallman
2021-08-25 8:37 ` Michalis V.
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=e8c9b19b-b59c-8a1e-353a-6180e98b7dbc@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=11912@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mvar.40k@gmail.com \
--cc=rms@gnu.org \
--cc=schwab@linux-m68k.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).