From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 49869@debbugs.gnu.org
Subject: bug#49869: Revert buffer? Yes/No/Maybe
Date: Wed, 04 Aug 2021 23:43:43 +0300 [thread overview]
Message-ID: <87lf5h53u0.fsf@mail.linkov.net> (raw)
In-Reply-To: <83pmutl8iv.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 04 Aug 2021 15:05:44 +0300")
> Since we now have the use-short-answers option, why is it a problem to
> have to confirm, if you could make it a single key?
The problem is that by default the length of the key sequence
when the user decides to revert the current buffer
is 7 keys:
'C-x x g y e s RET'
With the patch provided by Gregory the default length
will be reduced to 4 keys:
'C-x x g y'
or to 3 keys when there are no unsaved changes.
The yes/no question is still asked when revert-buffer
is called automatically - that makes sense.
But when the user decided to revert the buffer explicitly,
why require to type more keys?
next prev parent reply other threads:[~2021-08-04 20:43 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
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 [this message]
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=87lf5h53u0.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=49869@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 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).