On Mon, 26 Jul 2021, Dominique Michel wrote:

> Le Mon, 26 Jul 2021 10:15:08 +0100 (BST),
> Mark Hills <m...@xwax.org> a écrit :
> 
> > My keyboard and mouse are on a USB hub, powered on/off separately.
> > I'm tired of having to manually re-run a script every time I return
> > to work.
> > 
> > Searching gives suggestions to add scripts to Linux udev; that seems 
> > totally the wrong layer to me -- it can only be configured by root,
> > runs whether X is running or not, and I'd somehow need to delegate
> > access to the running X session. I don't run dbus here either. This
> > is on simple Slackware/Alpine Linux system.
> 
> I would say than the best way is to let X to manage the mouse and the
> pointer. As example, I have nothing special for the USB mouse, it just
> work, and for the keyboard I have a file
> /etc/X11/xorg.conf.d/30-keyboard.conf
> 
> Section "InputClass"
>       Identifier "evdev keyboard  catchall"
>       MatchIsKeyboard "on"
>       MatchDevicePath "/dev/input/event*"
>       Driver "evdev"
>       Option "XkbLayout" "ch"
>       Option "XkbVariant" "fr"
>       Option "XkbRules" "xorg"
> EndSection

Thanks for the suggestion.

I'm reluctant to push these to system settings, as they're personal onces 
I should be able to move around in my $HOME folder (and in my previous 
employer I could not even have adjusted this configuration) -- but I can 
see what you are saying.

I suppose I'd need to work out the equivalent of xmodmap in these Xkb* 
settings, as well as the other settings:

  xmodmap ~/.xmodmap         # custom layout
  xset r rate 300 100        # keyboard repeat
  xset m 0.4                 # mouse acceleration
  xsetwacom --set "Wacom One by Wacom M Pen stylus" MapToOutput DisplayPort-0

The X server could really be more helpful here: "xset r" is presented as a 
global setting, yet it sets the current keyboards, not newly added ones. 
Same for "xset m" with mice.

What do fvwm users do if they have a custom keyboard layout?

-- 
Mark

Reply via email to