jbuski / shellinabox

Automatically exported from code.google.com/p/shellinabox
Other
0 stars 0 forks source link

<>^`$£¨!-_ keys dont work with Firefox and swiss german keyboard #289

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
the keys   < >    ^`    $£     -_  do not work in Firefox (Version 38.0.5) and 
Swiss German Keyboard (under OS X 10.10.4) I got it working by editing 
vt100.jspp but its now specific to firefox and some things like [ or ] don't 
work now under Safari and look like deadkey's there. So someone with more 
experience in this code should fix it properly for all browsers and keyboards.

Anyhow, here's the mapping I figured out

for Firefox under OS X with Swiss German Keyboard

Output  Keypress  In Firefox
±       ALT 1     event.altKey, ch=1
“       ALT 2     event.altKey, ch=2
#       ALT 3     event.altKey, ch=3
Ç       ALT 4     event.altKey, ch=4
[       ALT 5     event.altKey, ch=5
]       ALT 6     event.altKey, ch=6
|       ALT 7     event.altKey, ch=7
{       ALT 8     event.altKey, ch=8
}       ALT 9     event.altKey, ch=9
≠       ALT 0     event.altKey, ch=0
@       ALT G     event.altKey, ch='G'
<       <         key=60
>       SHIFT <   event.shiftKey, key=60
$       $         key=164
£       SHIFT $   event.shiftKey, key=164
^       ^         key=161
`       SHIFT ^   event.shiftKey, key=161 (normally a dead key)
¨       ¨         key=160 (normally a dead key)
!       SHIFT ¨   event.shiftKey, key=160
-       -         key=173
_       SHIFT -   event.shiftKey, key=173

There's a lot more on the keyboard but these are the most important ones to do 
anything useful in the shell (like what do you do without '-' ? That key is 
totally dead otherwise).

Original issue reported on code.google.com by af...@datacell.com on 22 Jun 2015 at 11:29

Attachments:

GoogleCodeExporter commented 8 years ago
Hello, we should have this fixed on our fork of shellinabox. Please check 
https://github.com/shellinabox/shellinabox. 

If you still find any problems please report the issue on Github and we will 
take a look :)

Original comment by luka.kra...@gmail.com on 23 Jun 2015 at 7:28