all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>,
	Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: 68663@debbugs.gnu.org
Subject: bug#68663: Unsaved buffers dialog is unhelpful
Date: Sat, 27 Jan 2024 13:18:07 -0800	[thread overview]
Message-ID: <CADwFkmnBdgF9ySru2K2L1SYxujWZ8v8Sg_bEmaafjaXRJYOvMw@mail.gmail.com> (raw)
In-Reply-To: <86r0i27pop.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
>> Date: Sat, 27 Jan 2024 18:21:35 +0300
>> Cc: 68663@debbugs.gnu.org
>>
>> Right, makes sense.
>>
>> What about improving the current dialog, restoring at least some of the
>> pre-29 behavior?
>>
>> Maybe add some option that allows jumping into the save-some-buffers
>> buffers prompt.
>
> I'd prefer to hear more opinions.  The change which you dislike was
> done on purpose, so I'm reluctant to revert it unless enough people
> agree with you.
>
> Stefan, WDYT?

I'd rather not go back on that change, indeed.  It was done not only on
purpose, but after a discussion where all involved welcomed the change:
https://debbugs.gnu.org/4980

I think this is a wontfix at this point.  Sorry, Nikolay.





  reply	other threads:[~2024-01-27 21:18 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 [this message]
2024-01-27 22:38             ` Nikolay Kudryavtsev
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=CADwFkmnBdgF9ySru2K2L1SYxujWZ8v8Sg_bEmaafjaXRJYOvMw@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=68663@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=nikolay.kudryavtsev@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.