From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: 68663@debbugs.gnu.org
Subject: bug#68663: Unsaved buffers dialog is unhelpful
Date: Sun, 28 Jan 2024 01:38:56 +0300 [thread overview]
Message-ID: <81ca484b-c26b-4798-9a75-4ac5b1c54eab@gmail.com> (raw)
In-Reply-To: <CADwFkmnBdgF9ySru2K2L1SYxujWZ8v8Sg_bEmaafjaXRJYOvMw@mail.gmail.com>
That's very unfortunate.
I'll summarize the arguments for changing this dialog for the future,
because I have a hunch that this would eventually be changed:
From the point of view of a power user this is bad because power users
generally have Emacs running for day-weeks-months at a time and they
generally need to know whether the change they've made to some buffer
days ago is meaningful or a typo. The new behavior requires them to set
use-dialog-box nil or remember about the C-x C-c behavior being
different. All for a basic thing that ideally should not take any mental
space.
From the point of view of a new user this is bad because now the user
is stuck searching for those modified buffers by hand since Emacs have
not given him any guidance. Quitting and saving is such a basic
operation(cue two pages of vim jokes) that at this point we should not
only not expect the user to know about M-x save-some-buffers, but even
what the buffer modified mode line flag looks like.
next prev parent reply other threads:[~2024-01-27 22:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 20:37 bug#68663: Unsaved buffers dialog is unhelpful Nikolay Kudryavtsev
2024-01-22 23:41 ` Dmitry Gutov
2024-01-27 11:08 ` Eli Zaretskii
2024-01-27 14:40 ` Nikolay Kudryavtsev
2024-01-27 14:54 ` Eli Zaretskii
2024-01-27 15:21 ` Nikolay Kudryavtsev
2024-01-27 15:37 ` Eli Zaretskii
2024-01-27 21:18 ` Stefan Kangas
2024-01-27 22:38 ` Nikolay Kudryavtsev [this message]
2024-01-27 23:31 ` Stefan Kangas
2024-01-28 17:21 ` Nikolay Kudryavtsev
2024-01-28 5:54 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81ca484b-c26b-4798-9a75-4ac5b1c54eab@gmail.com \
--to=nikolay.kudryavtsev@gmail.com \
--cc=68663@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefankangas@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 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.