From: Juri Linkov <juri@linkov.net>
To: pinkanon pinkanon <pinkanon.pinkanon@yandex.ru>
Cc: "34939@debbugs.gnu.org" <34939@debbugs.gnu.org>
Subject: bug#34939: Some minibuffer behaviour is annoying
Date: Mon, 01 Apr 2019 23:25:08 +0300 [thread overview]
Message-ID: <87r2alcyuj.fsf@mail.linkov.net> (raw)
In-Reply-To: <26451261554113450@myt6-add70abb4f02.qloud-c.yandex.net> (pinkanon pinkanon's message of "Mon, 01 Apr 2019 13:10:50 +0300")
>>> (2) When I try to quit and some buffer is unchanged, I get the usual
>>> deal asking me what I want. The problem I have here [in addition to
>>> the problem discussed in (1), adapted to this case: "Type C-h for
>>> help."] is that I must use C-g, but not good old escape.
>>
>> To avoid all such problems, just bind keyboard-escape-quit globally
>> when not on a tty where an ESC prefix still might be needed:
>>
>> (when window-system
>> (define-key global-map [escape] 'keyboard-escape-quit))
>
> I have no luck w/ this one, though. Emacs 26.1 build 1, Arch Linux.
> steps: emacs -Q somefile -> Eval the code -> type something ->
> C-x C-c -> "Save file...? ..." -> Escape -> "Type C-h for help"
Thanks for detailed test case, I misunderstood your original description,
but now it's clear.
`C-x C-c' (save-buffers-kill-terminal) is a special case that
requires a special customization:
(define-key query-replace-map [escape] 'quit)
next prev parent reply other threads:[~2019-04-01 20:25 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 19:13 bug#34939: Some minibuffer behaviour is annoying pinkanon pinkanon
2019-03-22 16:57 ` Dmitry Gutov
2019-03-23 2:32 ` Richard Stallman
2019-03-23 9:46 ` Dmitry Gutov
2019-03-23 9:50 ` Eli Zaretskii
2019-03-23 11:24 ` Dmitry Gutov
2019-03-23 12:18 ` pinkanon pinkanon
[not found] ` <<83o961q5rr.fsf@gnu.org>
2019-03-23 15:51 ` Drew Adams
2019-03-31 19:50 ` Juri Linkov
2019-03-31 19:49 ` Juri Linkov
2019-03-31 20:29 ` Juri Linkov
2019-04-01 13:08 ` Dmitry Gutov
2019-04-01 20:31 ` Juri Linkov
2019-04-01 21:53 ` Dmitry Gutov
2019-04-03 20:50 ` Juri Linkov
2019-05-19 20:16 ` Juri Linkov
2019-04-01 10:10 ` pinkanon pinkanon
2019-04-01 20:25 ` Juri Linkov [this message]
2019-04-02 18:25 ` pinkanon pinkanon
2019-04-01 13:03 ` Dmitry Gutov
2019-04-01 20:29 ` Juri Linkov
2019-04-07 20:43 ` Juri Linkov
2019-04-07 23:09 ` Dmitry Gutov
2019-04-08 19:47 ` Juri Linkov
2019-04-08 22:00 ` Drew Adams
2019-04-08 23:06 ` Dmitry Gutov
2019-04-08 23:32 ` Drew Adams
2019-04-08 23:37 ` Dmitry Gutov
2019-04-08 23:59 ` Drew Adams
2019-04-09 0:11 ` Dmitry Gutov
2019-04-09 18:26 ` Drew Adams
2019-05-24 22:49 ` Dmitry Gutov
2019-05-27 20:15 ` Juri Linkov
2019-05-27 20:58 ` Dmitry Gutov
2019-05-29 21:53 ` Juri Linkov
2019-05-29 22:26 ` Drew Adams
2019-05-30 19:50 ` Juri Linkov
2019-05-30 21:00 ` Drew Adams
2019-05-30 21:35 ` Juri Linkov
2019-06-03 20:27 ` Juri Linkov
2019-06-04 15:15 ` Dmitry Gutov
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=87r2alcyuj.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=34939@debbugs.gnu.org \
--cc=pinkanon.pinkanon@yandex.ru \
/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).