| 1 |
Le Mercredi 17 Mai 2006 22:44, Benno Schulenberg a écrit : |
| 2 |
> Hi all, |
| 3 |
> |
| 4 |
> This is absurd, but when in bash-3.1_p17 I press Shift+M, the "M" |
| 5 |
> only appears the moment I press another key. This happens both in |
| 6 |
> Konsole and on a VT. And also in xterm and rxvt. |
| 7 |
> |
| 8 |
> It happens also in bash-3.1_p14 and bash-3.0-r14. And sash-3.7-r1. |
| 9 |
> But _not_ in bash-2.05b-r11, nor in tcsh-6.14-r3, nor in zsh-4.2.5. |
| 10 |
> Also typing in vim or nano works fine, and in KMail and KWrite and |
| 11 |
> Firefox and Konqueror. So this is purely a problem of the bash-3.* |
| 12 |
> series. |
| 13 |
> |
| 14 |
> I tried different CFLAGS (-O2 instead of -Os), a different compiler |
| 15 |
> (gcc-3.3.6-vanilla instead of 3.4.6-hardened), no difference. I've |
| 16 |
> tried starting bash with '--noprofile --norc', even with 'env -i', |
| 17 |
> it all makes no difference: any first press of Shift+M does not |
| 18 |
> show an M; only the next keypress makes the M appear. |
| 19 |
> |
| 20 |
> Is anyone else seeing this? Or am I going bananas? |
| 21 |
> |
| 22 |
> Benno |
| 23 |
|
| 24 |
I have come across that kind of behaviuour when I was playing with unicode |
| 25 |
settings. It happened when I was using a unicode console with a non unicode |
| 26 |
keymap. However, it only happened on accented characters (the ones composed |
| 27 |
with a dead key of course, but also all the other ones !). |
| 28 |
|
| 29 |
The thing I can tell you is that I have no such problem with bash-3.1_p16, |
| 30 |
compiled with gcc-3.4.5-r1 and glibc 2.3.6-r3. All three of them have |
| 31 |
the "nls" usflag enabled. |
| 32 |
|
| 33 |
Are you sure there are not any app on your system that capture this specific |
| 34 |
combination ? |
| 35 |
|
| 36 |
What keymap are you using ? |
| 37 |
|
| 38 |
|
| 39 |
-- John |
| 40 |
|
| 41 |
|
| 42 |
-- |
| 43 |
gentoo-user@g.o mailing list |
Archives