unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Josselin Poiret via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>,
	"Maxime Devos" <maximedevos@telenet.be>
Cc: 56139-done@debbugs.gnu.org
Subject: [bug#56139] [PATCH 0/4] Make window managers use libinput-minimal instead of libinput
Date: Sun, 26 Jun 2022 12:14:57 +0200	[thread overview]
Message-ID: <8735fru3xa.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87zgi2t7uu.fsf@gnu.org>

Hi Ludo and Maxime, 

Ludovic Courtès <ludo@gnu.org> writes:
> Since it’s under libexec/, I’d assume that it’s not meant to be invoked
> directly, but the man page suggests otherwise?…

Just as a heads-up, the debug GUI is supposed to be launched through
`libinput debug-gui`.  I'm not sure there's anything there that cannot
be debugged through `libinput debug-envents` though.

Cheers,
-- 
Josselin Poiret




      reply	other threads:[~2022-06-26 10:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 12:14 [bug#56139] [PATCH 0/4] Make window managers use libinput-minimal instead of libinput Josselin Poiret via Guix-patches via
2022-06-22 12:17 ` [bug#56139] [PATCH 1/4] gnu: wlroots: Replace input libinput by libinput-minimal Josselin Poiret via Guix-patches via
2022-06-22 12:17 ` [bug#56139] [PATCH 2/4] gnu: sway: " Josselin Poiret via Guix-patches via
2022-06-22 12:17 ` [bug#56139] [PATCH 3/4] gnu: waybar: " Josselin Poiret via Guix-patches via
2022-06-22 12:17 ` [bug#56139] [PATCH 4/4] gnu: hikari: " Josselin Poiret via Guix-patches via
2022-06-23 20:20 ` bug#56139: [PATCH 0/4] Make window managers use libinput-minimal instead of libinput Ludovic Courtès
2022-06-23 20:34   ` [bug#56139] " Maxime Devos
2022-06-24 15:10     ` Ludovic Courtès
2022-06-26 10:14       ` Josselin Poiret via Guix-patches via [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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8735fru3xa.fsf@jpoiret.xyz \
    --to=guix-patches@gnu.org \
    --cc=56139-done@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=ludo@gnu.org \
    --cc=maximedevos@telenet.be \
    /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).