From: Lars Ingebrigtsen <larsi@gnus.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "Michalis V." <mvar.40k@gmail.com>, 11912@debbugs.gnu.org
Subject: bug#11912: 24.1; 'M' in Dired on a symlink does not refresh the display
Date: Thu, 26 Aug 2021 15:52:34 +0200 [thread overview]
Message-ID: <8735qw2tzx.fsf@gnus.org> (raw)
In-Reply-To: <ab82ce58-70f5-a56d-f6a5-1d1c5acf58c3@cs.ucla.edu> (Paul Eggert's message of "Wed, 25 Aug 2021 10:59:23 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
> Yes, that's what POSIX requires. However, Dired is different from the
> POSIX shell, because a Dired user sees the permissions on a symbolic
> link while typing the command to the edit permissions, and the natural
> assumption is that one is editing what one is seeing. This is even
> more true of Wdired (Bug#50189); and it's also quite true for Dired.
Yeah, that's a good point.
> That is why G, O, T should also be fixed (see Bug#50191). The Dired
> users sees the group, ownership, and timestamp of the symlink while
> typing the "change the group" (or whatever) command, so the natural
> assumption is that one is changing what one is seeing.
Yup.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-08-26 13: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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735qw2tzx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=11912@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=mvar.40k@gmail.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.