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: Sun, 03 Mar 2024 19:55:15 +0200 [thread overview]
Message-ID: <86wmqjjj3w.fsf@mail.linkov.net> (raw)
In-Reply-To: <864jdnnrd6.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 03 Mar 2024 19:43:17 +0200")
>> Like Michael suggested a set of functions should be created.
>> These functions should share the same prefix.
>>
>> So the whole set of functions will be:
>>
>> revert-buffer-state-functions
>> revert-buffer-state-read-only
>> revert-buffer-state-outlines
>> ...
>>
>> Or like the variable 'preserve-modes' hints above,
>> the common prefix could be like this:
>>
>> revert-buffer-preserve-functions
>> revert-buffer-preserve-modes
>> revert-buffer-preserve-read-only
>> revert-buffer-preserve-outlines
>> ...
>>
>> Which prefix would you prefer?
>
> How about revert-buffer-restore- ?
"restore" would be only part of the truth,
because these functions first save the state,
only their second task is to restore the saved state
afterwards.
next prev parent reply other threads:[~2024-03-03 17: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 [this message]
2024-03-03 18:46 ` Eli Zaretskii
2024-06-03 6:35 ` Juri Linkov
2024-06-03 16:55 ` Juri Linkov
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=86wmqjjj3w.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.