From: Maxime Devos <maximedevos@telenet.be>
To: Rene Saavedra <nanuui@protonmail.com>, 55235@debbugs.gnu.org
Subject: [bug#55235] [PATCH] gnu: Add touchegg.
Date: Wed, 04 May 2022 15:51:38 +0200 [thread overview]
Message-ID: <5a4692cb2ee05aba388724a634936a6a629da904.camel@telenet.be> (raw)
In-Reply-To: <L6NN4nckg3RjiT_mmJGG2L3bRKBOeJijnKl_GAG7jHoCPggBAc7ZkMrbjFMX4tOd7l2-Jvyk_8CaOpvNwDLmvJZC5GBkisJz1CjBEmmmbNE=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
> + diff --git a/gnu/packages/toys.scm b/gnu/packages/toys.scm
Doesn't look like a toy to me.
Rene Saavedra via Guix-patches via schreef op di 03-05-2022 om 01:01
[+0000]:
> + ;; gnome-shell launch touchegg binary on startup and
> + ;; touchegg requires root privileges for proper
> functioning.
> + (add-after 'unpack 'disable-autostart
> + (lambda _
> + (substitute* "installation/touchegg.desktop"
> + (("Exec=touchegg")
> + "Exec=false")))))))
What does it need root for?
> + (synopsis "Linux multi-touch gesture recognizer")
Is it Linux-specific? Also, does it work in a pure environment (./pre-
inst-env guix shell --pure touchegg -- touchegg)?
> use libinput to communicate with +hardware.")
The exact library used seems like an implementation detail to me.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-05-04 13:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 1:01 [bug#55235] [PATCH] gnu: Add touchegg Rene Saavedra via Guix-patches via
2022-05-04 13:51 ` Maxime Devos [this message]
2022-05-07 21:53 ` Rene Saavedra via Guix-patches via
2022-05-08 10:58 ` Maxime Devos
2022-05-15 15:46 ` Rene Saavedra via Guix-patches via
2022-05-18 22:24 ` Rene Saavedra via Guix-patches via
2022-05-20 18:39 ` Rene Saavedra via Guix-patches via
2022-06-04 15:56 ` bug#55235: " Julien Lepiller
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5a4692cb2ee05aba388724a634936a6a629da904.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55235@debbugs.gnu.org \
--cc=nanuui@protonmail.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/guix.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).