all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "VÖRÖSKŐI András" <voroskoi@gmail.com>
Cc: 66932@debbugs.gnu.org
Subject: [bug#66932] [PATCH] services: Add xremap service.
Date: Sat, 02 Dec 2023 11:48:30 +0100	[thread overview]
Message-ID: <87o7f8hoch.fsf@gnu.org> (raw)
In-Reply-To: <57d94dcb19152592014053ef0bc81e95e4f6b602.1699111054.git.voroskoi@gmail.com> ("VÖRÖSKŐI András"'s message of "Sat, 4 Nov 2023 16:17:35 +0100")

Hi András,

VÖRÖSKŐI András <voroskoi@gmail.com> skribis:

> * gnu/services/desktop.scm (<xremap-configuration>): New record.
> (xremap-shepherd-service): New procedure.
> (xremap-service-type): New variable.
> * doc/guix.texi (Desktop Services): Document this.
>
> Change-Id: I76f9e238c72fb47226140e2b86dd9490cd9c9351

Nice!

> +(append
> +  (list
> +   (service xremap-service-type
> +                    (xremap-configuration
> +                     (config-file (plain-file "xremap.yml"
> +"modmap:
> +  - name: Global
> +    remap:
> +      CAPSLOCK:
> +        held: CONTROL_L
> +        alone: Esc
> +        alone_timeout_millis: 1000"))))

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.)

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

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.

Thanks,
Ludo’.




  reply	other threads:[~2023-12-02 10:49 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 [this message]
2023-12-04 17:43   ` VÖRÖSKŐI András

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

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

  git send-email \
    --in-reply-to=87o7f8hoch.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=66932@debbugs.gnu.org \
    --cc=voroskoi@gmail.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.