unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 50189@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>,
	Arthur Miller <arthur.miller@live.com>
Subject: bug#50189: wdired chmod should not follow symlinks (Bug#11912 followup)
Date: Sun, 11 Sep 2022 13:05:32 +0200	[thread overview]
Message-ID: <87o7vmgohv.fsf@gnus.org> (raw)
In-Reply-To: <87mtb6zoed.fsf@web.de> (Michael Heerdegen's message of "Sun, 11 Sep 2022 03:32:42 +0200")

Michael Heerdegen <michael_heerdegen@web.de> writes:

>> Setting wdired-allow-to-change-permissions to t or `advanced' made this
>> work -- you can't really edit the permissions without that.
>
> That behavior not optimal and a bit confusing.

Yeah, like a lot of stuff with dired and wdired, unfortunately.

> I think we could make wdired explicitly check for and throw a
> "user-error" in this case so that the editing command is not performed
> (but only after the properties were attached).

You mean in the wdired-allow-to-change-permissions nil case?  Yes,
definitely.





  reply	other threads:[~2022-09-11 11:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-24 18:04 bug#50189: wdired chmod should not follow symlinks Paul Eggert
2021-08-25 11:47 ` bug#50189: wdired chmod should not follow symlinks (Bug#11912 followup) Lars Ingebrigtsen
2022-09-10  6:28   ` Lars Ingebrigtsen
2022-09-11  1:32     ` Michael Heerdegen
2022-09-11 11:05       ` Lars Ingebrigtsen [this message]
2022-09-10  6:21 ` Lars Ingebrigtsen

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=87o7vmgohv.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=50189@debbugs.gnu.org \
    --cc=arthur.miller@live.com \
    --cc=eggert@cs.ucla.edu \
    --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 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).