From: Lars Ingebrigtsen <larsi@gnus.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 50189@debbugs.gnu.org
Subject: bug#50189: wdired chmod should not follow symlinks (Bug#11912 followup)
Date: Sat, 10 Sep 2022 08:28:02 +0200 [thread overview]
Message-ID: <87czc3oia5.fsf@gnus.org> (raw)
In-Reply-To: <87pmu1kapc.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 25 Aug 2021 13:47:27 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Yeah, editing the permissions doesn't seem to work for me in dired. If
> I start with
>
> -rw-r--r-- 1 larsi larsi 329K Aug 21 18:22 IMG_4478.JPG
>
> and press DEL after the final dash, it'll delete the dash and then say
> "Text is read only", leaving me with:
>
> -rw-r--r- 1 larsi larsi 329K Aug 21 18:22 IMG_4478.JPG
>
> And then I can't insert anything there, because it's now read-only. So
> something is wonky in the way wdired tries to make certain bits of the
> line read-only.
Setting wdired-allow-to-change-permissions to t or `advanced' made this
work -- you can't really edit the permissions without that.
So I guess there's nothing more to be done here...
next prev parent reply other threads:[~2022-09-10 6:28 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 [this message]
2022-09-11 1:32 ` Michael Heerdegen
2022-09-11 11:05 ` Lars Ingebrigtsen
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=87czc3oia5.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=50189@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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).