Shift/Ctrl + F keys not working about terminology HOT 13 CLOSED

I should have fixed it in df59f16. Thank you.

from terminology.

Sorry for the delay in responding - you patched it so quickly! Thank you!

Unfortunately it's still a bit off. Now ctrl+F2 will output ';5~' and shift+F2 will generate ';2~' right on the command line. It seems the escape sequences aren't completely making it to byobu/tmux?

Thanks!

from terminology.

Can you tell me which terminal emulator you currently use to do that?

from terminology.

I usually use gnome-terminal or just straight up VTs on servers. Byobu is only a wrapper for tmux or screen. Double checking I was able to use it on xfce terminal, sakura and guake. I think all those terminals (other than the non-X VTs) use libvte.

As a side note terminology won't accept input from input methods like iBus. Not that I'm using iBus when inputting shift+f keys or ctrl+f keys, but the issues could be related?

from terminology.

You should run:
ECORE_IMF_MODULE=ibus terminology

from terminology.

If you're using enlightenment, you should set it there, in settings → Language → Input Method Settings

from terminology.

I hate to say it but using ECORE_IMF_MODULE=ibus doesn't allow me to use it. Same with setting Input Method Settings (which I had already set up). Thing is I'm using a Japanese keyboard and I switch with the hankaku/zenkaku key... perhaps this the keycode is being eaten by terminology?

I'll fork and see if I can build and debug a bit. Don't have a lot of free time so I can't make any promises but I'll do my best.

from terminology.

I'm having trouble getting a clean build right now (moved on to Ubuntu 14.04 and there are some issues with enlightenment core libs and libpoppler). Regardless I think I may have found the issue.

While the individual key codes are the same, gnome-terminal and the like are interpreting say Shift+F2 as ^[O1;2Q but we're sending ^[[12;2~. I'm trying to figure out exactly where this mapping changed but I found a few snippets here and there of different projects changing over - mostly with comments suggesting VT220 or greater compatibility.

I think the key codes you added are for a different VT spec, whereas xterm and derivatives seem to be roughly shooting for VT220ish style. The most concise list of the key codes I think we're looking for were here: http://www.geocities.jp/sakachin2/xehelp/html/HID00000438.htm . I just wish I could find an actual document giving and actual full overview of the VT220 spec and how it differs... and perhaps some description somewhere of how xterm etc. are matching the spec or where they are not.

from terminology.

About ibus, you should ask on the enlightenment mailing list or on irc.
I will try to look into the issue with Ctrl/Shift this weekend.

from terminology.

I'll look into iBus myself first. It may be an unrelated thing and I actually have a suspicion about it.

Thanks again for being so proactive in handling this issue. I hope I'm not taking up much of your free time.

from terminology.

Someone reported the same issue without using ibus so it seems unrelated.

from terminology.

Aah, good. I had a suspicion it was unrelated and I had a suspicion it was related to dbus - as I was getting dbus errors which I initially assumed were unrelated but looking deeper it seems some enlightenment related libraries I have were compiled with an older/incompatible version of the dbus libs. Sorry to waste your time with the iBus red herring.

from terminology.

In 5bf2692, I should have fixed the issue with F1-4. Please tell me if it works better.

from terminology.