On Sun, Feb 02, 2020 at 09:08:33AM -0500, 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
That could be this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495435 e.g., if xterm is confused about the screensize due to this race (which is hard to fix due to the interaction between X11, Xt libraries and the window manager -- there's _always_ a delay). As a workaround, just typing "resize" should fix that. If you happen to see the problem again, it's worth a moment to verify. fwiw, I do this: resize -s 40 80 to get a 40x80 screen (works _all_ the time :-) -- Thomas E. Dickey <dic...@invisible-island.net> https://invisible-island.net ftp://ftp.invisible-island.net
signature.asc
Description: PGP signature
_______________________________________________ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
