unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Phil Sainty <psainty@orcon.net.nz>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
Subject: Re: Horrible new unsaved buffers dialog
Date: Sat, 29 Jan 2022 13:53:17 +1300	[thread overview]
Message-ID: <6869a836e575f52f40023f78f4f0a1c5@webmail.orcon.net.nz> (raw)
In-Reply-To: <87pmocge2v.fsf@gnus.org>

On 2022-01-29 02:55, Lars Ingebrigtsen wrote:
> The old dialog box was incomprehensible and user hostile.

I think the old dialog box was for the *most* part both
comprehensible and (by providing useful options) user friendly.

The button I'd consider removing is "save this but no more",
because the user isn't being shown which other buffers that
will affect.  Of course "No for all" is the same, but the
latter is saying "I don't care about this session" whereas
the former suggests that the user does care about the session
to some extent.  Others might disagree, though.

"View this buffer and quit" is a useful button, but worded
in a confusing way, as "quit" could either mean "exit emacs"
or "do not exit emacs".  The "exit emacs" interpretation
doesn't make a lot of sense in context, and yet if the user
doesn't *want* to exit emacs they are going to be hesitant
to make assumptions.  Perhaps "Edit this buffer" would be a
better label.

I think that everything else is both useful and very clear.

The new dialog is unquestionably a lot simpler, but I don't
think that's a good thing.  If the reason for this change is
that other programs don't have "quit" dialogs which are useful
as the Emacs version, I don't think that's a good reason to
make the Emacs version less useful.  I would instead argue
that other programs would benefit from more useful dialogs.

I think the original dialog could be improved by making it
more *sophisticated* by providing the user with an overview
of all the unsaved buffers, but IMO this extreme simplification
is a step backwards.

The original dialog provided a streamlined way for the user
to do all the sorts of things which they will likely need
to do in this situation.  By removing those options you haven't
removed the user's need to do those things, but you've made
it harder for them to do it.


-Phil




  parent reply	other threads:[~2022-01-29  0:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87y230iqfr.fsf.ref@yahoo.com>
2022-01-28  1:45 ` Horrible new unsaved buffers dialog Po Lu
2022-01-28 13:55   ` Lars Ingebrigtsen
2022-01-28 20:10     ` Tomas Hlavaty
2022-01-28 20:14       ` Tomas Hlavaty
2022-01-29  9:07       ` Sergey Organov
2022-01-29  0:52     ` Po Lu
2022-01-29 14:39       ` Lars Ingebrigtsen
2022-01-29 21:48         ` Phil Sainty
2022-01-30 15:57           ` Lars Ingebrigtsen
2022-01-31  0:35             ` Po Lu
2022-01-31  0:45               ` Phil Sainty
2022-01-31  2:21                 ` Po Lu
2022-01-31 15:30                   ` Lars Ingebrigtsen
2022-01-30  1:00         ` Po Lu
2022-01-29  0:53     ` Phil Sainty [this message]
2022-01-29 10:40 xenodasein--- via Emacs development discussions.
2022-01-29 11:39 ` Po Lu

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=6869a836e575f52f40023f78f4f0a1c5@webmail.orcon.net.nz \
    --to=psainty@orcon.net.nz \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.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).