ctrl-a-d sequence when using screen

[GoogleCodeExporter]

What steps will reproduce the problem?
1. When opening a screen session the way to get out of it would be to press and 
hold the ctrl key with the `a` and then release, followed by the `d` key.
2.
3.

What is the expected output? What do you see instead?
expected is to get out of screen, but instead you just see `ad`

What version of the product are you using? On what operating system?
3.0.1

Please provide any additional information below.

Original issue reported on code.google.com by angelo.m...@gmail.com on 18 Jul 2011 at 8:34

[GoogleCodeExporter]

Which ssh application are you using? See 
http://code.google.com/p/hackerskeyboard/wiki/FrequentlyAskedQuestions#Some_keys
_don't_work,_for_example_Ctrl-C/Ctrl-V_for_cut& - Hacker's Keyboard contains a 
special workaround for ConnectBot, but that doesn't help for other applications 
which don't support the keys. See also issue 36.

Original comment by Klaus.We...@gmail.com on 18 Jul 2011 at 9:26

[GoogleCodeExporter]

I'm using Irssi, which is based on Connectbot, so it should work, shouldn't it?

Original comment by angelo.m...@gmail.com on 18 Jul 2011 at 9:38

[GoogleCodeExporter]

Sorry, "based on" is currently insufficient, the code checks for the specific 
package name. I'll look into making this configurable, or at least add handling 
for irssi.

Does pressing the trackball (dpad center) also work as a Ctrl key equivalent in 
irssi? That's the workaround the keyboard uses for ConnectBot.

Original comment by Klaus.We...@gmail.com on 18 Jul 2011 at 9:50

[GoogleCodeExporter]

Can you please try v1.21rc3 (or later) from 
http://code.google.com/p/hackerskeyboard/downloads/list ? It activates the 
workarounds for the irssi and pslib connectbot variants.

Original comment by Klaus.We...@gmail.com on 18 Jul 2011 at 11:41

• Changed state: Accepted

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have my F keys going to different screens within 'screen'.

F1 - F5 = broke
F6 - F9 = work
F10 = seen as F8
F11 = broke
F12 = broke

Cntrl key doesnt work.

any plans to make all of these things work properly in connectBot?
im using v1.21rc4

Original comment by tgwa...@gmail.com on 30 Aug 2011 at 8:40

[GoogleCodeExporter]

I've changed the function key handling, the current Market version v1.22 should 
work better. Note that this is based on heuristics and may not work correctly 
depending on your target system - the keyboard just sends raw sequences based 
on current settings.

If it's still causing problems, please file a new bug - especially regarding 
the Ctrl key issue. Make sure you've switched on the "ConnectBot tab hack" if 
you have problems.

Original comment by Klaus.We...@gmail.com on 26 Sep 2011 at 9:08

• Changed state: Fixed

[GoogleCodeExporter]

After switched on the "ConnectBot tab hack" F10 - fixed but stop works "tab"

Original comment by ATD...@gmail.com on 15 Oct 2011 at 7:46

[GoogleCodeExporter]

Bulk update - changing "Fixed" to "Verified" for old bugs.

(Background: I'm changing the "Fixed" status to be considered open, the next 
steps in the lifecycle will be the closed states "FixInTest" and "Verified". 
This lets me mark issues as "Fixed" in commit messages without hiding them from 
the issue tracker.)

Original comment by Klaus.We...@gmail.com on 22 Jan 2013 at 7:33

[GoogleCodeExporter]

Bulk update - changing "Fixed" to "Verified" for old bugs.

Original comment by Klaus.We...@gmail.com on 22 Jan 2013 at 7:34

• Changed state: Verified