From: Michael Heerdegen <michael_heerdegen@web.de>
To: Tianxiang Xiong <tianxiang.xiong@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Persistent transient keymap for mouse scrolling
Date: Tue, 23 May 2017 23:55:26 +0200 [thread overview]
Message-ID: <87shjvkzld.fsf@drachen> (raw)
In-Reply-To: <CACMkxiw9TXmOCRFxgag=mEWiTGZ5jbPn4CKDCrnUGv0EzWFARQ@mail.gmail.com> (Tianxiang Xiong's message of "Sun, 14 May 2017 15:47:41 -0700")
Tianxiang Xiong <tianxiang.xiong@gmail.com> writes:
> In an Emacs StackExchange
> <https://emacs.stackexchange.com/questions/32765/persistent-transient-keymap-for-mouse-scrolling>
> question,
> I found that it's difficult to create a transient keymap that persists
> for
> scroll events and exits for other keys/events.
>
> What *is* the best way to do this?
Did you try to follow the advice from Stefan's crystal ball?
Michael.
prev parent reply other threads:[~2017-05-23 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 22:47 Persistent transient keymap for mouse scrolling Tianxiang Xiong
2017-05-23 21:55 ` Michael Heerdegen [this message]
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=87shjvkzld.fsf@drachen \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=tianxiang.xiong@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.
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).