From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: Robert Marshall <robert.marshall@codethink.co.uk>,
Lars Ingebrigtsen <larsi@gnus.org>,
29412@debbugs.gnu.org
Subject: bug#29412: 27.0.50; dired-toggle-read-only should (at some point!) check that the direcory is writeable
Date: Sun, 13 Dec 2020 21:58:45 +0200 [thread overview]
Message-ID: <87im95eb0j.fsf@mail.linkov.net> (raw)
In-Reply-To: <5aa02c80-bcf2-4e99-915b-013275f3328d@default> (Drew Adams's message of "Sun, 13 Dec 2020 08:55:36 -0800 (PST)")
>> Then maybe better would be to ask a y-or-n question
>> whether the user still wants to edit the unwritable buffer.
>
> I disagree. This should be handled _exactly_ the
> same way we handle a buffer for a file that is
> read-only. I see no argument why we should treat
> a directory buffer different from a file buffer.
Asking a y-or-n question is _exactly_ what
'C-x C-q' does in wdired, i.e. after typing
'C-x C-q' (wdired-exit) it asks a question:
Buffer modified; save changes? (y or n)
So now entering wdired mode does the same thing with
'C-x C-q' (dired-toggle-read-only):
Directory isn't writable; edit anyway? (y or n)
next prev parent reply other threads:[~2020-12-13 19:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 16:11 bug#29412: 27.0.50; dired-toggle-read-only should (at some point!) check that the direcory is writeable Robert Marshall
2020-12-12 11:33 ` Lars Ingebrigtsen
2020-12-12 19:26 ` Drew Adams
2020-12-13 8:32 ` Juri Linkov
2020-12-13 13:18 ` Lars Ingebrigtsen
2020-12-13 17:00 ` Drew Adams
2020-12-13 19:04 ` Robert Marshall
2020-12-13 16:55 ` Drew Adams
2020-12-13 19:58 ` Juri Linkov [this message]
2020-12-13 21:45 ` Drew Adams
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=87im95eb0j.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=29412@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
--cc=robert.marshall@codethink.co.uk \
/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).