From: npostavs@users.sourceforge.net
To: Yujie Zhou <zhou@lorentz.leidenuniv.nl>
Cc: 24339@debbugs.gnu.org
Subject: bug#24339: 24.5; Need double c-g to quit from a minibuffer
Date: Wed, 31 Aug 2016 21:41:54 -0400 [thread overview]
Message-ID: <87shtkpfa5.fsf@users.sourceforge.net> (raw)
In-Reply-To: <5737c5f3-21ea-b2f1-0b61-5aa312a703c5@lorentz.leidenuniv.nl> (Yujie Zhou's message of "Tue, 30 Aug 2016 09:47:45 +0200")
Yujie Zhou <zhou@lorentz.leidenuniv.nl> writes:
> Dear Emacs maintainers,
>
> on this device I need double pressing C-g to quit from a minibuffer,
> even starting from 'emacs -Q'. More specifically, after pressing C-x
> C-f, if I do not realease the control botton, I only need one C-g to
> quit the minibuffer. But if I realease, I need two. If I only press
> C-g
> once, the minibuffer shows the text quit, but the cursor is still
> focused on the minibufer, and I have to press C-g again within 3
> seconds, otherwise the Find-File minibuffer reappears after the text
> quit fades in 3 seconds. And in that case, I need to double-press
> again to quit.
You've mentioned at http://emacs.stackexchange.com/a/26715/5296
I solved this myself by switching off the option of Show position of
pointer when the Control key is pressed in Linux mouse setting. I
guess there is some conflict between Emacs and this option.
so it seems some OS feature might be modifying the keystrokes that Emacs
sees. Can you show the contents <f1> l (view-lossage) after you've hit
C-g with this option on?
next prev parent reply other threads:[~2016-09-01 1:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 7:47 bug#24339: 24.5; Need double c-g to quit from a minibuffer Yujie Zhou
2016-09-01 1:41 ` npostavs [this message]
[not found] ` <3da9d864-d731-dec4-b0a2-cb7a7c7ff38d@lorentz.leidenuniv.nl>
2016-09-05 0:31 ` Noam Postavsky
2016-09-08 0:35 ` npostavs
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=87shtkpfa5.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=24339@debbugs.gnu.org \
--cc=zhou@lorentz.leidenuniv.nl \
/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.