Package: shellinabox
Version: 2.14-1
Severity: normal

Debian version: 8.1
Kernel version: 3.16.0-4-kirkwood #1 Debian 3.16.7-ckt11-1 (2015-05-24) armv5tel GNU/Linux

Hi,

I also have in Jessie (and have always had, with Lenny then Wheezy) this issue with shellinabox.
I use a French keyboard, and the characters that do not work for me are:

— symbol: ) FR key: )         Corresponding US key: -
— symbol: ° FR key: Shift + ) Corresponding US key: -
— symbol: ] FR key: AltGr + ) Corresponding US key: -
— symbol: } FR key: =         Corresponding US key: =
— symbol: $ FR key: $         Corresponding US key: ]
— symbol: £ FR key: Shift + $ Corresponding US key: ]
— symbol: ¤ FR key: AltGr + $ Corresponding US key: ]
— symbol: ù FR key: ù         Corresponding US key: '
— symbol: % FR key: Shift + ù Corresponding US key: '
— symbol: * FR key: *         Corresponding US key: #
— symbol: µ FR key: Shift + * Corresponding US key: #
— symbol: < FR key: <         Corresponding US key: \
— symbol: > FR key: Shift + < Corresponding US key: \
— symbol: : FR key: :         Corresponding US key: .
— symbol: / FR key: Shift + : Corresponding US key: .
— symbol: ! FR key: !         Corresponding US key: /
— symbol: § FR key: Shift + ! Corresponding US key: /

For some reason, though, sometimes the "}" becomes available...

I let you imagine how frustrating it can be to interact with the shell without * ] } $ : / (thankfully, * an / work on the numeric keypad). And in a general manner, the lack of ) is also a bit distressing :-D

The US key correspondence is given to give an indication about the physical location on the keyboard. For this correspondence, I used this reference:
http://www.bristol.ac.uk/it-services/learning/documentation/keyboard-1/keyboard-r1-6.gif
which is the QWERTY keyboard which is the closest I could find to the physical layout of a typical AZERTY keyboard.

Yves.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to