From: Davin Pearson <davin.pearson@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: How to rebind the QUIT button on the GUI.
Date: Sat, 29 Dec 2018 19:40:20 -0800 (PST) [thread overview]
Message-ID: <6ac7f323-193e-4ac6-9584-e208c234fc2e@googlegroups.com> (raw)
My current quit button on the Emacs GUI asks for a directory using the mouse. It asks me for a directory to save the *Message* buffer and another buffer such as *Compile-Log* etc.
This is not ideal behavior since buffers whose buffer name starts and ends with a * should be killed and not saved.
The ideal behavior would not ask for a directory to save the *Message* buffer.
I also prefer the modeline for asking such questions.
next reply other threads:[~2018-12-30 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 3:40 Davin Pearson [this message]
2018-12-30 15:08 ` How to rebind the QUIT button on the GUI ken
2018-12-30 22:56 ` Michael Heerdegen
2018-12-30 23:59 ` Drew Adams
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=6ac7f323-193e-4ac6-9584-e208c234fc2e@googlegroups.com \
--to=davin.pearson@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).