From: "Ludovic Courtès" <ludo@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, Alex Kost <alezost@gmail.com>
Subject: Re: 07/07: services: console-keymap: Deprecate.
Date: Fri, 12 Apr 2019 23:09:56 +0200 [thread overview]
Message-ID: <87wojzkk0r.fsf@gnu.org> (raw)
In-Reply-To: <875zrkx9ry.fsf@netris.org> (Mark H. Weaver's message of "Thu, 11 Apr 2019 22:00:06 -0400")
Hi Mark,
Mark H Weaver <mhw@netris.org> skribis:
> Well, I described adding custom keybindings to the console keymap, for
> which I cannot find any examples in the manual. I see only examples of
> using the pre-existing layouts, variants, and options that are built in
> to XKB.
>
> On the other hand, I just found that adding:
>
> (keyboard-layout (keyboard-layout "us" #:options '("ctrl:nocaps")))
>
> has the effect of adding all of the keyboard bindings that I personally
> want.
Yes, that’s the one I had in mind.
> For the curious: the "custom" bindings I wanted are just those that Xorg
> has by default, but that are missing from the default console keyboard
> map. Most notably, I had found that many (most?) Meta+Shift keyboard
> combinations did not work properly in Emacs at the console, until I
> added my "custom" bindings. However, these missing bindings are
> installed when my OS config has the above 'keyboard-layout' line.
Great, I’m glad this works for you.
> So, thank you for implementing this new keyboard configuration system,
> which is clearly a great improvement over what we had before, and which
> now allows me to remove rather large section of my OS config that held
> my keyboard map.
>
> On the other hand, if this new system does not support custom keymaps,
> it would be good to keep the old console-keymap-service around, even if
> tucked in a back room, renamed, and clearly marked "only for hackers".
> However, I don't feel strongly about it. As you say, hackers can cook
> up their own private service if they need to, I suppose.
Yeah, I’m not opposed to keeping ‘console-keymap-service’ if people are
find XKB configuration too limiting. I just don’t want it to be the
first thing newcomers stumble upon when looking for ways to configure
their keyboard.
Thanks,
Ludo’.
prev parent reply other threads:[~2019-04-12 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190405134511.7740.88403@vcs0.savannah.gnu.org>
[not found] ` <20190405134516.BD1962158A@vcs0.savannah.gnu.org>
2019-04-06 1:45 ` 07/07: services: console-keymap: Deprecate Mark H Weaver
2019-04-06 19:51 ` Alex Kost
2019-04-07 16:24 ` Ludovic Courtès
2019-04-11 19:04 ` Alex Kost
2019-04-12 21:01 ` Ludovic Courtès
2019-04-12 2:00 ` Mark H Weaver
2019-04-12 21:09 ` Ludovic Courtè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=87wojzkk0r.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).