From: Gregory Heytings <gregory@heytings.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: juri@linkov.net, 49869@debbugs.gnu.org
Subject: bug#49869: Revert buffer? Yes/No/Maybe
Date: Wed, 04 Aug 2021 12:37:43 +0000 [thread overview]
Message-ID: <ab91551b30e13297bf5d@heytings.org> (raw)
In-Reply-To: <83im0ll7oi.fsf@gnu.org>
>> (defun revert-buffer-short-answer (&optional args)
>> (interactive (list (not current-prefix-arg)))
>> (let ((use-short-answers t))
>> (revert-buffer args)))
>>
>> (global-set-key (kbd "C-x x g") 'revert-buffer-short-answer)
>
> If you propose this as something people who want this could do in their
> init files, then I agree.
>
No, I propose this as a solution to Juri's problem, instead of his
proposed solution to "revert the buffer immediately" with C-x x g, which
is indeed too drastic. Something even better to take Lars' suggestion (do
not ask confirmation when the buffer has not been modified) into account:
(defun revert-buffer-short-answer (&optional ignore-auto noconfirm preserve-modes)
(interactive (list (not current-prefix-arg)))
(let ((use-short-answers t)
(noconfirm (not (buffer-modified-p))))
(revert-buffer ignore-auto noconfirm preserve-modes)))
next prev parent reply other threads:[~2021-08-04 12:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 8:45 bug#49869: Revert buffer? Yes/No/Maybe Juri Linkov
2021-08-04 9:02 ` Lars Ingebrigtsen
2021-08-04 10:06 ` Gregory Heytings
2021-08-04 9:03 ` Andreas Schwab
2021-08-04 12:05 ` Eli Zaretskii
2021-08-04 12:22 ` Gregory Heytings
2021-08-04 12:23 ` Eli Zaretskii
2021-08-04 12:37 ` Gregory Heytings [this message]
2021-08-04 12:53 ` Eli Zaretskii
2021-08-04 13:30 ` Gregory Heytings
2021-08-05 10:43 ` Lars Ingebrigtsen
2021-08-05 11:08 ` Gregory Heytings
2021-08-06 9:21 ` Lars Ingebrigtsen
2021-08-10 7:12 ` Juri Linkov
2021-08-10 14:40 ` bug#49869: [External] : " Drew Adams
2021-08-10 14:41 ` Lars Ingebrigtsen
2021-08-04 20:43 ` Juri Linkov
2021-08-05 5:48 ` Eli Zaretskii
2021-08-05 23:33 ` Juri Linkov
2021-08-06 6:20 ` Eli Zaretskii
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=ab91551b30e13297bf5d@heytings.org \
--to=gregory@heytings.org \
--cc=49869@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
/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).