unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Richard Stallman <rms@gnu.org>
Cc: mvar.40k@gmail.com, 11912@debbugs.gnu.org, eggert@cs.ucla.edu
Subject: bug#11912: 24.1; 'M' in Dired on a symlink does not refresh the display
Date: Thu, 26 Aug 2021 15:54:36 +0200	[thread overview]
Message-ID: <87y28o1fc3.fsf@gnus.org> (raw)
In-Reply-To: <E1mJ6Wd-0004uX-Fw@fencepost.gnu.org> (Richard Stallman's message of "Wed, 25 Aug 2021 23:57:59 -0400")

Richard Stallman <rms@gnu.org> writes:

> I wouldn't assume that a user who uses M on a symlink in Dired wants
> to alter the file it points to.  I think it is more likely that the
> user did not realize it might do that.  Suppose you operate on 10
> files and one is a symlink -- you might not even have noticed that one
> is as symlink.

Yes, that's a good point.  It's always ambiguous what the user really
wants to do when doing operations on symlinks, and making Dired always
"edit what's actually in the buffer" (i.e., the symlink itself) makes it
less ambiguous (even if it might surprise people who expected Posix
semantics).

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-08-26 13:54 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 [this message]
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=87y28o1fc3.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=11912@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=mvar.40k@gmail.com \
    --cc=rms@gnu.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).