Re: Mouse stopped working in MC

[Adam Pribyl <pribyl lowlevel cz>]

On Sun, 2 Feb 2020, Frank McCormick wrote:

> On 2/2/20 6:04 AM, Yury V. Zaytsev wrote:
> > I would be careful about assigning blame with xterm maintainer also 
> > reading this list ;-) Maybe we are doing something that gets xterm 
> > confused... do you have a way of consistenly reproducing the problem?
> >
> > On Sun, 2 Feb 2020, Adam Pribyl wrote:
> >
> > > Is it reproducible? This happens from time to time, but is not mc 
> > > fault but xterm. It shoul help to reset the term with "reset" command.
> > >
> > > On Sat, 1 Feb 2020, Frank McCormick wrote:
> > >
> > > >  I am running Debian Sid fully updated. My mouse has stopped
> > > >  working in MC. Instead I get key codes on the MC command line.
> > > >  I normally run MC in an xterm.
> > > >
> > > >  How do I go about resolving this.
>
> On my machine, if I go into /usr/bin and run xterm directly, THEN run mc 
> (or mc -x) the mouse works properly. However
> if I pass any parameters to xterm, such as -g 150x40 -e mc
> then the mouse stops working and I get keycodes on the
> mc command line.
>
> I should note that I get into /usr/bin by running this small
> script.
>
> cd ~
> xterm -g 153x40+150+20 -fn 10x20
>
> I do this because I run rox-filer to put icons on the desktop
> with Icewm.
>
> Since this problem started, I have changed running xterm to
> running lxterm (for a unicode env) and the problem has
> disappeared.

xterm should be also utf8 capable, if this is enabled during build 
(ctrl+right click should shoul utf8 stuff - if this is enough). I also use 
IceWm on Fedora and I am not able to reproduce it this way, but I know it 
happens from time to time...

> > The problem has been resolved but I don't understand what is happening 
> or why.
>
> Frank