Can't enter certain "shifted" characters about irssiconnectbot

[zorun]

Same issue here.

This bug was introduced by the last update of Irssi Connectbot (i.e. less than a few weeks ago)

Basically, the keys '!', '$', '&', '(' and ')' do not produce any character (with '&' acting like TAB instead)

I'm having the issue on a HTC Wildfire (soft keyboard)

[woltage]

https://github.com/irssiconnectbot/irssiconnectbot/ICB_ver_390_RC1.apk/qr_code

[zorun]

Awesome, thanks! That fixes it.

[asturur]

Hi all,
i'm fighting with connect bot irssi lately.

This update on 25 november changed the way my hardware keyboard ( connected with USB or BT ) behave on connectbot-irssi.

First i had CTRL+SHIFT+1 = F1 ... CTRL+SHIFT+2 =F2 etc etc

Now SHIFT+2= F2 and i can't use ANY shifted character on the numbers.

Thanks everyone for your attention.

[woltage]

Which device you are using? I just bought USB plugin for Galaxy tab 10.1. So I will debug this issue.

[asturur]

Oh thank you very much.
I'm trying both on asus transformer t101 and acer iconia, both are with
nvidia tegra 2.

On asus trasformer just bluetoot keyboard from logitech ( ps3 keyboard )
On Acer iconia both bluetooth from logitch and usb keyboard from dell (
very standard one ).

I have cobol software i run from terminal wich tell me the value of each
key when i press them.
both f1 - f12 are producing no value ( as if the keypress disappear
somewhere from they keyboard to the terminal emu )
pag up pag down no value as well.

Is there anyway to pass they key value from the keyboard directly to the
terminal? like special function direct hardware keyboard?

2011/12/4 Iiro Uusitalo <
[email protected]

Which device you are using? I just bought USB plugin for Galaxy tab 10.1.
So I will debug this issue.

---

Reply to this email directly or view it on GitHub:

#12 (comment)

[asturur]

Any news about this topic?

[woltage]

@asturur are the newest release working? Can you confirm that?

[asturur]

I left the tablet in the office, i can tell you monday, sorry.

[asturur]

Huge leap forward.
F1-F10 ok using CTRL 1 - CTRL 0 ( not direct fn keys but ok )
pgup pgdown OK

Esc key not working again. older version worked. now i have to touch the screen to get ESC , is this a "known issue" or is just a "feature" ?
and still i don't understand how to get out from the shift key toggle function.

Probably is my fault i started the software it was on vt100 emulation mode, everything worked, but not the esc
( that is intercepted by irssiconnectbot )

Then i switched to xterm emulation mode and then went back to vt100
but i could not more input SHIFT + Number keys, i don't know why.
Couldn't go out from the situation in wich you press shift key and the cursor on screen rotates with different triangles on top or bottom.
Is there any manual to read?

[lizsugar]

I actually just encountered the same issue today with my bluetooth microsoft wedge keyboard my nexus 10. Ctrl codes were being passed through just fine, but now irssi connectbot insists on stealing them and bring up things like the copy function and the url search function. Both of which completely kill productivity and making working on the command line impossible.

Edit: I should say that it was working fine for about two and a half hours before this started. I tried rebooting, turning the keyboard on and off.. yet it persists.

Update: OK, it looks like it thinks my hardware keyboard is some sort of software keyboard. Double tapping shift puts it into capslock mode. This would also explain why shift+ any numbers doesn't produce the related symbols, since that doesn't do anything on soft keyboards. Problem is, I don't know how to make it realize I'm using a hardware keyboard. These issues don't manifest in any other app on my tablet. Everything works just fine except for irssi connectbot. Will need to play around and dig some more.

Update 12/12/12: Hah, I figured out why it happens to me:

If I start an ssh connection while my hardware keyboard is on and synced to my tablet, it treats it as a software keyboard (double tap shift = caps, shift + numbers = no symbols). If I start the ssh session while the keyboard is off and turn it on after the connection has been established, it behaves as expected.

I haven't been able to logcat this yet, but that's what I've found out instead of going to sleep at reasonable times.