Arch Linux User Repository

@devnoname120 I don't think I will, honestly. It works well-enough for me as is... and since a few weeks ago I switched to QWERTY-Lafayette and I'm not even using this layout anymore :/

@Schnouki Could you do an upstream PR to add base.lst updating? Thanks

@fenouil I played a bit with strace and it looks like it only tries to read variants from /usr/share/X11/xkb/rules/base.lst. But the install script (from upstream) doesn't update that file... so localectl doesn't see qwerty-fr.

I'll file an upstream bug about this.

After installing, I can bind to this layout in sway config and it is working as expected.

Nethertheless, I can't find the new layout using the following commands:

$ localectl list-keymaps | grep us
amiga-us
atari-us
br-latin1-us
cz-us-qwertz
is-latin1-us
mac-us
sunt5-cz-us
sunt5-us-cz
us
us-acentos
us1



$ localectl list-x11-keymap-variants us
alt-intl
altgr-intl
chr
colemak
colemak_dh
colemak_dh_iso
dvorak
dvorak-alt-intl
dvorak-classic
dvorak-intl
dvorak-l
dvorak-mac
dvorak-r
dvp
euro
haw
hbs
intl
mac
norman
olpc2
rus
symbolic
workman
workman-intl

Any ideas ?

Thanks @devnoname120 for the new release and the outdated notification!

So: new AUR package release!

Update to new upstream qwerty-fr 0.6: now released via github

• the debian install scripts didn't change at all from 0.5
• the debian package now contains .xz files instead of .gz files
• less confusing .install messages

Known issues:

• upgrading from <=0.5-3 will log an error (pre-upgrade): workaround:
  • uninstall the package
  • reset patched files by reinstalling xkeyboard-config
  • install the package

• upgrading from 0.5 won't immediately apply the new layout workarounds:

  • either: setxkbmap -v -layout us_qwerty-fr
  • or, possibly better: sudo udevadm trigger --subsystem-match=input --action=change
  • (localectl doesn't reload the layout)

  I have no idea how it works, but the new solution with udevadm (from https://askubuntu.com/questions/968107/how-can-i-reload-my-xkb-configuration-without-restarting-my-computer-or-logging#comment2312806_1075707) seems to work and be cleaner than setxkbmap.

I could not easily search on other AUR keyboard layout packages if the usage of udevadm is standard or not. What do the internet think about including that in the package? Or print a message mentioning it?

Moved scripts to /usr/share/libalpm/scripts as apparently lots of packages are doing that.

@bda, not sure what your issue is, but I doubt it's caused by this package :/

Hi, since some week, some characters do not work as expected. cedila for example. Euro symbol. When i type one of them, the focus keep on the text area (or terminal, vim, ...). Mouse pointer work but no click. I can only do a CTRL+ALT+Fx for opening another VT and reboot the computer.

I find it OK to put it in /usr/share/libalpm/scripts and call it there from the install file; that's what us_da-layout does, and it helps normalizing packages too !

Also, us_da-layout has an exta

pre_upgrade() {
    pre_remove
}

which may be useful to us: we install again on post_upgrade, but do not clean before.

I wondered about the location for those scripts too. But since they are also called by the install file, it seemed weird to me to put them in /usr/share/libalpm/scripts.

How would you feel about /usr/share/xkb-qwerty-fr?

@Schnouki thanks for your work !

The us_da-layout package is indeed inspiring. It has the advantage of not patching /usr/share/X11/xkb/symbols/us but our upstream .deb postinst/postrm handle it well anyway it seems.

One little suggestion: maybe put our scripts in /usr/share/libalpm/scripts/ like us_da-layout does instead of /usr/bin? I have not read the libalpm doc around that though...