all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: 68663@debbugs.gnu.org
Subject: bug#68663: Unsaved buffers dialog is unhelpful
Date: Sat, 27 Jan 2024 16:54:35 +0200	[thread overview]
Message-ID: <86v87e7ro4.fsf@gnu.org> (raw)
In-Reply-To: <6593db7e-a065-4d07-89e8-775f7e8cd90e@gmail.com> (message from Nikolay Kudryavtsev on Sat, 27 Jan 2024 17:40:32 +0300)

> From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
> Date: Sat, 27 Jan 2024 17:40:32 +0300
> Cc: 68663@debbugs.gnu.org
> 
> So the big question here is this: what's going to be the dev team's 
> decision on the idea of getting rid of the pop up dialog entirely and 
> replacing it with C-x C-c(save-some-buffers) minibuffer prompt?

You can have it already in your customizations: set use-dialog-box to
nil.

Getting rid of dialog boxes entirely is out of the question, since
Emacs always prompts with a dialog box when some command was invoked
from the menu bar by clicking the mouse.  This is very old behavior,
and we cannot change it, not even for a single command.  Sorry.





  reply	other threads:[~2024-01-27 14:54 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 [this message]
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
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=86v87e7ro4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=68663@debbugs.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.