unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tomas Hlavaty <tom@logand.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Horrible new unsaved buffers dialog
Date: Fri, 28 Jan 2022 21:10:49 +0100	[thread overview]
Message-ID: <87r18rwrhy.fsf@logand.com> (raw)
In-Reply-To: <87pmocge2v.fsf@gnus.org>

On Fri 28 Jan 2022 at 14:55, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Po Lu <luangruo@yahoo.com> writes:
>
>> In this morning's master, it only shows a single "unsaved buffers"
>> dialog, which is completely inadequate when there is more than one
>> unsaved file.  I don't understand why this change was made which turns
>> said dialog box from a convenient feature into an eyesore.
>
> The old dialog box was incomprehensible and user hostile.

Why does Emacs pops up native dialog at all?

Even the minibuffer based version is not so convenient.

Would not it be better to show a new buffer listing all the unsaved
changes and relevant buttons in one place, not sequentially popping up
in dialog or minibuffer?

Something like:

Modified buffers exist.
  [Save all buffers and quit]
  [Exit anyway]
Save file /tmp/a?
  [Save]
  [Discard changes]
  [View]
  [View and quit]
  [View changes]
  [Save this but no more]
Save file /tmp/b?
  [Save]
  [Discard changes]
  [View]
  [View and quit]
  [View changes]
  [Save this but no more]
Save file /tmp/c?
  [Save]
  [Discard changes]
  [View]
  [View and quit]
  [View changes]
  [Save this but no more]



  reply	other threads:[~2022-01-28 20:10 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 [this message]
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
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=87r18rwrhy.fsf@logand.com \
    --to=tom@logand.com \
    --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).