Le Mercredi 17 Mai 2006 22:44, Benno Schulenberg a écrit : > Hi all, > > This is absurd, but when in bash-3.1_p17 I press Shift+M, the "M" > only appears the moment I press another key. This happens both in > Konsole and on a VT. And also in xterm and rxvt. > > It happens also in bash-3.1_p14 and bash-3.0-r14. And sash-3.7-r1. > But _not_ in bash-2.05b-r11, nor in tcsh-6.14-r3, nor in zsh-4.2.5. > Also typing in vim or nano works fine, and in KMail and KWrite and > Firefox and Konqueror. So this is purely a problem of the bash-3.* > series. > > I tried different CFLAGS (-O2 instead of -Os), a different compiler > (gcc-3.3.6-vanilla instead of 3.4.6-hardened), no difference. I've > tried starting bash with '--noprofile --norc', even with 'env -i', > it all makes no difference: any first press of Shift+M does not > show an M; only the next keypress makes the M appear. > > Is anyone else seeing this? Or am I going bananas? > > Benno
I have come across that kind of behaviuour when I was playing with unicode settings. It happened when I was using a unicode console with a non unicode keymap. However, it only happened on accented characters (the ones composed with a dead key of course, but also all the other ones !). The thing I can tell you is that I have no such problem with bash-3.1_p16, compiled with gcc-3.4.5-r1 and glibc 2.3.6-r3. All three of them have the "nls" usflag enabled. Are you sure there are not any app on your system that capture this specific combination ? What keymap are you using ? -- John -- [email protected] mailing list
