all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,
	Robert Marshall <robert.marshall@codethink.co.uk>
Cc: 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: Sat, 12 Dec 2020 11:26:37 -0800 (PST)	[thread overview]
Message-ID: <505c79af-0056-4f66-aca8-9559f6ef2bff@default> (raw)
In-Reply-To: <87y2i35ke7.fsf@gnus.org>

> I've now made `C-c C-q' signal an error if the directory isn't writable
> in Emacs 28.

I don't feel strongly about this, but I wonder whether
that's the right thing to do.  We do NOT do that for
files, for example.

The use cases, for files and directories too, I believe,
are these:

1. You can make changes in the buffer for other reasons,
with no intention to save.  You can do that to affect
information gathering, analysis, discovery, sorting,
searching whatever.

2. You can make changes and THEN make the file or dir
writable (inside or outside Emacs), and THEN save the
changes you've already prepared.

#2 can be handy in a situation where the resource is
shared, or where for some other reason you want to
minimize the time during which it is writable: you 
make it writable only for the duration of saving, not
for the entire time you do the editing.

Unless I'm missing some counter arguments, I'd say
this request and the "fix", though well-meaning, are
misguided.





  reply	other threads:[~2020-12-12 19:26 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=505c79af-0056-4f66-aca8-9559f6ef2bff@default \
    --to=drew.adams@oracle.com \
    --cc=29412@debbugs.gnu.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.