how to prevent roxterm from stealing focus while keying in unicode sequence?

[Mi605]

roxterm steals focus when keying in an unicode character in command line like ctrl+shift+u00ab in case the character code contains the letter “f”. E.g.: ctrl+shift+u1f60a will stop after “u1” and open the roxterm search field instead.

Is there a known workaround for this behaviour?

ROXterm version is the most recent version available in antiX 19.x, which means this is about ROXTerm 2.9.5 GTK 2/VTE 9 build

[realh]

In the current version you can let go of ctrl+shift after pressing u, then press ctrl+shift again after the hex code. That's a function of vte, and I don't know whether it worked like that back in version "9". If not, you could edit roxterm's keyboard shortcuts and make sure that ctrl-shift+A to F are all unmapped.

[Mi605]

Many thanks, realh! I can confirm, your recommended alternative input method, keying in ctrl+shift+u first, followed by the code itself while not pressing these two keys, works fine in ROXterm 2.9.5 version on antiX also. I just found out the input of the code sequence can get terminated either by ctrl+shift as you described, as well as by simply pressing the enter-key. No need to edit ROXterms shortcuts. Even if this behaviour is somewhat unusual, there is no problem, since this method works also while keying in the sequence in other programs (which allow the ctrl+shift being pressed all the time while keying the code, activating it by releasing the two buttons). Single thing to be observed is people need to know about this method, one could mention it in manpage or console help option.

Thank you very much for your great work, keeping ROXterm alive.