Closed GoogleCodeExporter closed 9 years ago
I tested this out just now and it works fine for both "alt" buttons + Q using
the ZSH
shell. I tried it on the Bash shell and it only works for the left "alt"+Q
button.
Pressing the right "alt" places a "/".
This problem looks more like a keymapping issue on Bash. But I didn't test it
out
for tcsh. This is definitely not 100% a ConnectBot problem.
Original comment by daveavila1@gmail.com
on 27 Dec 2008 at 5:11
If you look in settings, you'll notice an entry named "Directory shortcuts"
Basically it changes either the left or right side keys into alt -> / and shift
-> tab
You can disable this if you don't like it.
Original comment by kenny@the-b.org
on 19 Jan 2009 at 1:23
I'm experiencing this same issue, except instead of a slash, my tab characters
are ignored completely. This is on a Sony X10, using the Full Keyboard from
http://www.androlib.com/android.application.com-hmw-android-fullkeyboard-npwE.as
px
The tab key works when entering text into different apps, and I've also tried
using Ctrl-I, and Ascii character HT (0x09 for horizontal tab)
running "echo $HOST" prints out xterm (which is what I selected in connectbot
settings)
Original comment by jezte...@gmail.com
on 12 Jun 2010 at 1:15
Numerous threads have led my here, claiming post #2 by Kenny is the solution.
However, I have found this not to be the case. I am using a physical keyboard
with CTRL and TAB keys on it.
If I go to the ConnectBot settings and change "Directory shortcuts" to
"Disabled", it doesn't make the keyboard's TAB or CTRL keys work as TAB and
CTRL (which is what the original reporter was saying).
Yes, the setting works for switching the mapping of SHIFT & ALT between right
and left sides, or outright disabling it. However, it doesn't seem to have any
effect for actually restoring the functionality of the CTRL or ALT keys on the
physical keyboard.
This is the case for me at least, so I do not think this issue is "invalid" as
post #2 does not alleviate the actual problem.
Original comment by uncle...@gmail.com
on 10 Jan 2014 at 9:46
Original issue reported on code.google.com by
young...@gmail.com
on 19 Dec 2008 at 7:11