From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jasonspiro4@gmail.com, 4980@debbugs.gnu.org,
lennart.borgman@gmail.com, jasonr@f2s.com
Subject: bug#4980: 23.1.50; In File > Quit GUI, add "Cancel", write "Save", and simplify
Date: Fri, 28 Jan 2022 14:52:03 +0100 [thread overview]
Message-ID: <87tudoge7w.fsf@gnus.org> (raw)
In-Reply-To: <834k5oe3u9.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 28 Jan 2022 09:06:54 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> But save-some-buffers doesn't ask the same question: it asks about
> specific buffers, one by one. And popping 2 dialogs with basically
> the same question looks ... worse.
Yes, previously it was "Save file <...>" and "No for all", and then
"... exit anyway?". Since the first prompt is now "Close without
saving" it feels a bit more nagging?
But I think it still makes sense to ask twice, since it's pretty...
drastic? So I dunno. I don't have any strong opinion here -- what do
others feel? Should we keep the double prompt even though the first
prompt is now less cryptic?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-01-28 13:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 23:05 bug#4980: 23.1.50; In File > Quit GUI, add "Cancel", write "Save", and simplify Jason A. Spiro
2009-11-19 23:38 ` Lennart Borgman
2009-11-20 3:59 ` Jason Rumney
2009-11-20 4:31 ` Stefan Monnier
2022-01-27 18:55 ` Lars Ingebrigtsen
2022-01-27 19:56 ` Eli Zaretskii
2022-01-27 20:07 ` Eli Zaretskii
2022-01-27 21:27 ` Lars Ingebrigtsen
2022-01-28 7:06 ` Eli Zaretskii
2022-01-28 13:52 ` Lars Ingebrigtsen [this message]
2009-11-20 9:31 ` Juri Linkov
2009-11-20 9:55 ` Jan Djärv
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=87tudoge7w.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=4980@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jasonr@f2s.com \
--cc=jasonspiro4@gmail.com \
--cc=lennart.borgman@gmail.com \
/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).