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>, Juri Linkov <juri@linkov.net>
Cc: Robert Marshall <robert.marshall@codethink.co.uk>, 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 09:00:47 -0800 (PST)	[thread overview]
Message-ID: <de5b2008-f362-4c2d-aa24-1a0d6b2b7204@default> (raw)
In-Reply-To: <87ft494zfz.fsf@gnus.org>

> > OTOH, displaying a warning might go unnoticed by the user.
> >
> > Then maybe better would be to ask a y-or-n question
> > whether the user still wants to edit the unwritable buffer.
> 
> Makes sense.  I've now done this change.

Why do you keep making changes before even reading
responses or giving people a chance to respond?

Not one argument has been presented so far, by
anyone, as to why this case should be treated any
differently from the read-only file case.

I've given arguments why it should be treated the
same.  (They're the same arguments as would be
given for the file case.)





  reply	other threads:[~2020-12-13 17:00 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 [this message]
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=de5b2008-f362-4c2d-aa24-1a0d6b2b7204@default \
    --to=drew.adams@oracle.com \
    --cc=29412@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --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.