From: Paul Eggert <eggert@cs.ucla.edu>
To: Lars Ingebrigtsen <larsi@gnus.org>
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: Wed, 25 Aug 2021 10:59:23 -0700 [thread overview]
Message-ID: <ab82ce58-70f5-a56d-f6a5-1d1c5acf58c3@cs.ucla.edu> (raw)
In-Reply-To: <871r6hn64r.fsf@gnus.org>
On 8/25/21 3:57 AM, Lars Ingebrigtsen wrote:
> on the command line, chmod is fine with following symlinks
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.
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.
This assumption is so hardwired that it is the original motivation for
the coding error that prompted Bug#11912.
next prev parent reply other threads:[~2021-08-25 17:59 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 [this message]
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
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=ab82ce58-70f5-a56d-f6a5-1d1c5acf58c3@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=11912@debbugs.gnu.org \
--cc=larsi@gnus.org \
--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 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).