Issue with multilingual keyboard support, only in unprivileged bash, direct or X11 client
I noticed this strange behavior.
I installed French Canadian keyboard support with plain vanilla
configuration steps, i.e.
# loadkeys cf
for direct consoles (ones which reports ASCII or UTF-8 to a kbd_mode
in /etc/xorg.conf a line like
Option "XkbLayout" "pc+ca(fr)"
(this applies to bash in which kbd_mode reports raw or scancode mode)
This works fine in every contexts that I tested, except *unprivileged*
bash *when-it-reads-a-command-from-its-standard-input*. For instance,
$echo Montréal français
can not be typed due to the eacute character (echo Montral francais), but
works as expected, and a vim session also works.
Privileged (root) bash sessions work in Crux, and unprivileged sessions
in a Suse distribution also works.
Note that the special keystrokes sequences that generate a character
code *in-the-ASCII-range* works in every case, e.g. <AltCar> 2 generates
the @ character and ^ <space> ganerates ^ (^ e is expected to generate ê
It is not a serious issue for me, it just made my configuration
troubleshooting more tedious. Perhaps this strange behavior has other
side-effects, so I'm reporting this as seemingly Crux (2.4) specific.
P.S. If I may get an account for the wiki, I might report the kernel
config file that worked for my Lenovo T61 laptop installation.
- Thierry Moreau
CONNOTECH Experts-conseils inc.
9130 Place de Montgolfier
Canada H2M 2A1
web site: http://www.connotech.com
CRUX mailing list