Re: [Mlterm-dev-en] Broken behaviour with some key combinations!

[Mohammad_Alsaleh <ms...@to...>]

On Wed, May 15, 2013 at 09:20:30PM +0900, Araki Ken wrote:
>  Hi,
> 
> From: Mohammad_Alsaleh <ms...@to...>
> Subject: [Mlterm-dev-en] Broken behaviour with some key combinations!
> Date: Mon, 13 May 2013 02:03:54 +0300
> Message-ID: <1Ub...@in...>
> 
> > Last month, some key combinations' behaviour broke in my system.
> > Instead of executing assigned functionality (or doing nothing).
> > Weird escape sequences started to be printed instead.
> > 
> > ALT+Arrow_Key ;3A ;3B ;3C ;3D
> > Shift+Arrow_Key ;2A ;2B ;2C ;2D
> > Ctrl+Arrow_key ;5A ;5B ;5C ;5D
> >
> > * (A --> Up, B --> Down, C --> Right, D --> Left)
> >
> > I strongly suspected that an update to my system caused this.
> > 
> > To test my theory, I compiled older mlterm (minor) releases and they
> > all showed the same behaviour. The latest release itself (3.1.9) was
> > working just fine before this bug appeared.
> > 
> > Still, mlterm must be doing something wrong (or different) as it's
> > the only terminal emulator affected.
> 
>  I'm sorry but I still have no idea about the cause of this problem.
> 
>  Mlterm (and xterm) output these escape sequences ("^[[1;3A" etc)
> by default if combination keys doesn't match shortcut keys specified in
> ~/.mlterm/key.
> 

This happens with default configurations.

>  Do you mean that you assign these keys to the functions of some console
> applications like tmux and screen ?

Yes. I discovered the bug while using tmux. But then I carried my tests
outside tmux to make sure it's not at fault.

Only mlterm prints those symbols. Other terminal emulators don't print
anything. So, I'm assuming they're parsing the escape sequences
correctly. Only with Shift+Arrow_Key something is printed. But only a letter
(no ;2).

>  If so, which version do you use and how do you assign these keys ?
> 

I use latest tmux 1.8. This happens with default tmux (no user
configuration). I rolled back to 1.7 while testing and the result was
the same.

As I said, I had the same version of mlterm working before. So, I'm
suspecting some update in my system triggered the bug.

Many major components were updated to their latest version at the time
including glibc 3.17, GCC 4.8, glib2 2.36.x, gtk3 3.8.x among others.