On Tue, Aug 23, 2016 at 03:47:42PM +0200, Bill Allombert wrote:
Intrigued by Consolation as a possible GPM replacement, so I figured I'd
remove that and give it a shot.
Congratulation you are the first victim!
Fixed. ;)
BTW, copying a line works regardless of length, and the same for a word that
begins on or before column 64.
The code I use to get the screen size is as follow:
if (ioctl(0, TIOCGWINSZ, &s)) perror("TIOCGWINSZ");
screen_width = s.ws_col;
screen_height = s.ws_row;
That's strange because the value of 64 is never appropriate:
tjcarter@shiro:~$ echo `tty`: $TTY $COLUMNS $LINES
/dev/tty1: 160 64
tjcarter@shiro:~$ echo `tty`: $TTY $COLUMNS $LINES
/dev/tty2: 80 32
tty1 is using the default 8x16 font at 1280x1024. tty2 is using
TerminusBold's 16x32 option, so these numbers make sense at the
terminal.
And again, after fixing this (just re-run setupcon either as root or
from tty1) and restarting consolation, the consistent size for all
consoles does not help.
and I never expected the size of the linux console to change during
boot. I am not sure whether consolation will receive a SIGWINCH
in this case.
The problem seems to carry over even if the package is installed and
started on an already running system with consistent terminal sizes.
I do note that when the sizes are not consistent, consolation handled
64 lines on one tty and 32 lines on another just fine, however both
were limited to 64 columns.
In any case consolation should use the size of the terminal in use when
consolation is started. Could you check that ?
Yeah, I'd done that before I submitted the report. Mentioned the
rest about inconsistent ttys and 16x32 fonts because I thought it
might be relevant to tracking down something that might've gotten out
of sorts.
One thing I wonder about... I mention that the hardware believes
that I have two screens, one of which is 1024x768 dummy screen that
happens to not actually exist. I note that 1024/16 is 64. But then,
768/32 is only 24, and again it works on all 32 or 64 rows just fine
so I think this might be a red herring. And that ioctl should return
in information about the current tty which is not configured to use
the dummy screen at all.
Happy to help debug this if you've got some stuff you'd like me to
try/log/trace. I'm using a basic mouse here and GPM works fine, but GPM
hasn't really kept pace with modern input devices since 1997. My other
mouse is an Apple Magic Trackpad, etc. ;)
Also consolation is fully plug and play, there is no need to configure
the device.
I configured nothing--I looked to see if there was something I might
want to configure, but there wasn't.
Incidentally, I've removed gpm for testing consolation and will for the time
being remove consolation to restore gpm functionality. The package
indicates no need to do this, but it seems like a good idea. If that's
unnecessary, please let me know. Else I would suggest a change to the
manpage and control file.
Well, theoretically you could use gpm for one device and consolation for
the others but in practive it is better to disable gpm while using
consolation, otherwise you get two cursors which is confusing.
Maybe consolation should conflict with gpm at some point.
In any case to switch between gpm and consolation you can do
/etc/init.d/gpm stop
/etc/init.d/consolation start
systemctl blah blah systemd still gives me headaches. ;)
Any ideas?
Joseph
