From: martin rudalics <rudalics@gmx.at>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>,
"Alan Third" <alan@idiocy.org>,
"Lars Ingebrigtsen" <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Touch events
Date: Sun, 25 Jun 2017 19:10:05 +0200 [thread overview]
Message-ID: <594FEE6D.2040307@gmx.at> (raw)
In-Reply-To: <cf9a7b62-dd3b-62e1-bc6a-0617398936f1@gmail.com>
> The only trick I know of is to use show-help-function, which requires
> jumping through a bunch of annoying hoops. Maybe now is a good time
> to add an option to propagate these events to lisp? Maybe there should
> be a high-frequency-events list of symbols that includes which events
> should be propagated to Lisp? One pour (add-to-list
> 'high-frequency-events 'mouse-motion) to enable them, for example.
Why can't you use ‘track-mouse’ for that? Disregarding the fact that
movements below the smallest character size will not be propagated by
e.g. XTmouse_position anyway.
martin
next prev parent reply other threads:[~2017-06-25 17:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 8:53 Touch events Alan Third
2017-06-24 9:33 ` martin rudalics
2017-06-24 9:58 ` Alan Third
2017-06-24 13:18 ` Clément Pit-Claudel
2017-06-24 17:00 ` Lars Ingebrigtsen
2017-06-24 23:22 ` Alan Third
2017-06-24 23:43 ` Clément Pit-Claudel
2017-06-25 0:04 ` Lars Ingebrigtsen
2017-06-25 10:40 ` Alan Third
2017-06-25 16:56 ` Clément Pit-Claudel
2017-06-25 17:04 ` Noam Postavsky
2017-06-25 17:10 ` martin rudalics [this message]
2017-06-25 18:09 ` Clément Pit-Claudel
2017-06-25 19:22 ` Stefan Monnier
2017-06-26 10:08 ` Anders Lindgren
2017-06-26 18:28 ` Alan Third
2017-06-28 8:25 ` John Wiegley
2017-06-28 15:14 ` raman
2017-06-28 20:50 ` Alan Third
2017-09-03 9:14 ` Alan Third
2017-06-27 20:08 ` Alan Third
2017-06-28 9:40 ` Anders Lindgren
2017-06-28 17:23 ` James Nguyen
2017-06-28 21:06 ` Alan Third
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=594FEE6D.2040307@gmx.at \
--to=rudalics@gmx.at \
--cc=alan@idiocy.org \
--cc=cpitclaudel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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.
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).