From: Pierre Neidhardt <ambrevar@gmail.com>
To: Alex Dorof <axd@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: Setxkbmap :: Adding a custom xkb layout/variant :: Issue with specifying custom config path & wiping the cache
Date: Wed, 06 Jun 2018 10:20:04 +0200 [thread overview]
Message-ID: <87wovc72dn.fsf@gmail.com> (raw)
In-Reply-To: <8fef9b4d1f899c4570304edc57139b4c@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
Ha, I might have the perfect solution for you!
To sum up:
- You can't run at the system level (or even if you could, don't do it,
it's less flexible and more cumbersome to set up).
- If you redefine a keymap from scratch, you need to use xkbcomp, not
setxkbmap!
- If you only want to change some modifiers / options over a system
keymap, you can use a combination of setxkbmap and xmodmap.
See my dotfiles for an example:
https://github.com/ambrevar/dotfiles
In .xkb, I have defined a new "usim" keymap. The *.xkb file and the
symbols subfoler are mandatory.
To load the map, I call the following from `.xprofile`:
xkbcomp -I"$HOME/.xkb" "$HOME/.xkb/usim.xkb" $DISPLAY 2>/dev/null
I have more settings:
setxkbmap -layout us -variant ""
This resets the keymaps, it's useful when I do some live changes to my
keymap and they I can revert everything by simply sourcing `.xprofile`.
xcape -e 'Control_L=Escape'
Make Left Control (which is Caps Lock in my keymap) act as Escape when
not used as a modifier.
numlockx on
Turn on the numpad by default.
xbindkeys
Set additional keybindings such as the multimedia bindings as par the
`.xbindkeysrc` file.
Hope that helps!
--
Pierre Neidhardt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-06-06 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 23:36 Setxkbmap :: Adding a custom xkb layout/variant :: Issue with specifying custom config path & wiping the cache Alex Dorof
2018-06-06 8:20 ` Pierre Neidhardt [this message]
2018-06-07 13:03 ` Oleg Pykhalov
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=87wovc72dn.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=axd@disroot.org \
--cc=help-guix@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.
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).