From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: "50431@debbugs.gnu.org" <50431@debbugs.gnu.org>,
"juri@linkov.net" <juri@linkov.net>
Subject: bug#50431: revert-buffer doesn't preserve read-onlyness
Date: Fri, 26 Aug 2022 16:24:02 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488B81C7AD47D0EE58F789AF3759@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83tu5z1ds8.fsf@gnu.org>
> "Reverting" has a specific meaning: re-read the file from disk as if
> it were visited anew. If the user wants to make additional
> adjustments, they will need to readjust. I don't see why the
> read-only status should be exempt from this logic.
+1.
___
Consider Dired, which, by visiting a directory
is somewhat like visiting a file. Dired's `g'
reverts the buffer, but that doesn't revert
all of the Dired state (markings, sort order,
hidden files, etc.). `C-x C-v', on the other
hand, does "restore" to both revisit the file
system and restore Dired default (user) settings.
Both `g' and `C-x C-v' are useful in Dired.
Which is just another way of saying that there
can be multiple ways/kinds of "reverting".
next prev parent reply other threads:[~2022-08-26 16:24 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
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 [this message]
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
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=SJ0PR10MB5488B81C7AD47D0EE58F789AF3759@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=50431@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.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 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).