[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#29412: 27.0.50; dired-toggle-read-only should (at some point!) check
|
From: |
Drew Adams |
|
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) |
> > 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.)