unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "VÖRÖSKŐI András" <voroskoi@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 66932@debbugs.gnu.org
Subject: [bug#66932] [PATCH] services: Add xremap service.
Date: Mon, 04 Dec 2023 18:43:42 +0100	[thread overview]
Message-ID: <CXFQHUW0P46H.3GYTY9F2MXN8T@wasteland> (raw)
In-Reply-To: <87o7f8hoch.fsf@gnu.org>

Hi Ludo,

Thanks for the reply.

On Sat Dec 2, 2023 at 11:48 AM CET, Ludovic Courtès wrote:
> Hi András,
>
> Did you consider writing “bindings” so that one can configure it Scheme,
> as is the case for most other services?  (To be clear, I think we should
> still allow people to provide their own Yaml file as is done here.)

I did consider that, but I am not familiar with guile, so that is too
hard for me and there are a lot of combinations to handle.

> If that’s too tricky/impractical, we can keep the patch as is, but
> adding “native” configuration on top of that would be sweet.

It is tricky for me and telling the truth I do not see the benefit.

> I wonder if it would make sense, in a future patch, to also provide
> ‘home-xremap-service-type’ as a direct mapping of this service.  Food
> for thought.

I was thinking about that, but was not sure. There is a section in the README about that:
https://github.com/k0kubun/xremap#running-xremap-without-sudo

The basic idea is creating an input group with write permission for every
input type.
I think we can not automate the "add user to input group" in the home-service,
so that would be still a manual task.

Is this solution acceptable?

Thanks,
András




      reply	other threads:[~2023-12-04 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-04 15:17 [bug#66932] [PATCH] services: Add xremap service VÖRÖSKŐI András
2023-12-02 10:48 ` Ludovic Courtès
2023-12-04 17:43   ` VÖRÖSKŐI András [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=CXFQHUW0P46H.3GYTY9F2MXN8T@wasteland \
    --to=voroskoi@gmail.com \
    --cc=66932@debbugs.gnu.org \
    --cc=ludo@gnu.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/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).