From: Richard Stallman <rms@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: rgm@gnu.org, 50431@debbugs.gnu.org, juri@linkov.net
Subject: bug#50431: revert-buffer doesn't preserve read-onlyness
Date: Wed, 08 Sep 2021 23:07:35 -0400 [thread overview]
Message-ID: <E1mOAPX-0005Wx-VA@fencepost.gnu.org> (raw)
In-Reply-To: <87pmtkbcy4.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 07 Sep 2021 17:52:19 +0200)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> Making revert-buffer preserve user-initiated readedness changes isn't
> trivial. We'd need to record whether the buffer is read-only because it
> was read from a read-only file (and vice versa), and then use that data
> point in revert-buffer (to see whether we should respect the current
> readedness state or not).
How about just this: keep buffer-read-only unchanged?
If it differs from the file's permissions, almost certainly
the user changed it and will beglad of revert-buffer preserves it.
The other case is that the file permissions have been changed
since visiting the file. But users won't be shocked if
revert-buffer fails to change buffer-read-only in that case,
and they will know what to do.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2021-09-09 3:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 15:03 bug#50431: revert-buffer doesn't preserve read-onlyness Juri Linkov
2021-09-06 16:38 ` Glenn Morris
2021-09-07 15:52 ` Lars Ingebrigtsen
2021-09-09 3:07 ` Richard Stallman [this message]
2021-09-09 13:16 ` Lars Ingebrigtsen
2021-09-09 17:27 ` Juri Linkov
2022-08-24 11:35 ` Lars Ingebrigtsen
2022-08-24 17:12 ` Juri Linkov
2022-08-25 14:03 ` Lars Ingebrigtsen
2022-08-25 18:02 ` Juri Linkov
2022-08-25 18:55 ` Eli Zaretskii
2022-08-25 19:35 ` Juri Linkov
2022-08-26 5:34 ` Eli Zaretskii
2022-08-26 7:17 ` Juri Linkov
2022-08-26 16:10 ` Drew Adams
2022-08-26 10:41 ` Lars Ingebrigtsen
2022-08-26 10:48 ` Eli Zaretskii
2022-08-26 16:24 ` Drew Adams
2022-08-27 13:15 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1mOAPX-0005Wx-VA@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=50431@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=rgm@gnu.org \
/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.