all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 69511@debbugs.gnu.org
Subject: bug#69511: Restore any state after revert-buffer
Date: Mon, 03 Jun 2024 19:55:53 +0300	[thread overview]
Message-ID: <86v82qdkyu.fsf@mail.linkov.net> (raw)
In-Reply-To: <867cf7pqaj.fsf@mail.linkov.net> (Juri Linkov's message of "Mon,  03 Jun 2024 09:35:32 +0300")

close 69511 30.0.50
thanks

>> IMO, "restore" is better than "state", because you don't really
>> restore any state: a buffer has no state, per se.  "Restore" is also
>> better than "preserve".
>>
>> What is attractive in "restore" is that it is general and generic
>> enough to include all the meanings you have shown in your examples.
>> So I think "restore" is the best candidate till now.  If someone has
>> better suggestions, please speak up.
>
> Since no one has better suggestions, here is the patch that uses
> "restore".  This will create two different name prefixes:
>
>   revert-buffer-preserve-modes
>   revert-buffer-restore-read-only
>
> but this is fine.  So here is a complete patch with docs:

So now pushed, and closed.





  reply	other threads:[~2024-06-03 16:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-02 17:55 bug#69511: Restore any state after revert-buffer Juri Linkov
2024-03-02 18:11 ` Eli Zaretskii
2024-03-03  7:59   ` Juri Linkov
2024-03-03  9:04     ` Eli Zaretskii
2024-03-03 17:28       ` Juri Linkov
2024-03-03 17:43         ` Eli Zaretskii
2024-03-03 17:55           ` Juri Linkov
2024-03-03 18:46             ` Eli Zaretskii
2024-06-03  6:35               ` Juri Linkov
2024-06-03 16:55                 ` Juri Linkov [this message]
2024-03-03  2:46 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-03  7:55   ` Juri Linkov
2024-03-03  9:03     ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-04  6:37 ` Juri Linkov

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=86v82qdkyu.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=69511@debbugs.gnu.org \
    --cc=eliz@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.