unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: "T.V Raman" <raman@google.com>
Cc: monnier@iro.umontreal.ca,  emacs-devel@gnu.org
Subject: Re: Emacs, touchegg and touchpad events
Date: Fri, 24 Jun 2022 09:21:46 +0800	[thread overview]
Message-ID: <87wnd6g8k5.fsf@yahoo.com> (raw)
In-Reply-To: <25268.57899.246169.884276@retriever.mtv.corp.google.com> (T. V. Raman's message of "Thu, 23 Jun 2022 14:59:07 -0700")

"T.V Raman" <raman@google.com> writes:

> Interesting.
>
> Here is what I discovered next:
>
> Start touchegg as a daemon via systemctl -- it starts happily and runs
> but doesn't deliver events to emacs.

I'm going to guess that it's because Emacs is now using the X input
extension.

Try building --without-xinput2.

> Incidentally I looked through the emacs-29 touch code and it
> essentially does not work for me on my laptop's touchpad; the only
> event I can get emacs to see in that case (with no touchegg running)
> is the touch-end event sporadically showing up. Pinch etc dont appear
> to work.

What version of the X.Org server are you using?  As I said, you need
21.1.0 or later.



  reply	other threads:[~2022-06-24  1:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 17:43 Emacs, touchegg and touchpad events T.V Raman
2022-06-23  0:46 ` Po Lu
2022-06-23  2:41   ` T.V Raman
2022-06-23  3:10     ` Po Lu
2022-06-23 13:48       ` T.V Raman
2022-06-23 21:35         ` Stefan Monnier
2022-06-23 21:59           ` T.V Raman
2022-06-24  1:21             ` Po Lu [this message]
2022-06-24  1:20         ` Po Lu
2022-06-24  1:34           ` T.V Raman
2022-06-24  1:58             ` Po Lu
2022-06-24  6:09               ` Eli Zaretskii
2022-06-24  6:51                 ` Po Lu
2022-06-24 13:19               ` T.V Raman
2022-06-25  0:04                 ` Po Lu
2022-06-25 13:32                   ` T.V Raman
2022-06-23  7:57 ` Lars Ingebrigtsen
2022-06-23 13:50   ` T.V Raman
2022-06-24  1:23     ` Po Lu

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=87wnd6g8k5.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=raman@google.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.
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).