I'm going crazy trying to figure out how the hell a javascript console package (npm/blessed or better, the same but maintained npm/reblessed) is written, it's a mess, but that's my problem.
The real problem is that in xorg (xterm, xfce-terminal, etc) and in a remote console via ssh (windows terminal, putty, etc), everything seems to work. But in virtual terminal consoles (VT or ttyvN) the mouse stops working after column 94. I've also verified this with mc, htop and tmux and it does not work, but... in htop clicking after col 94 do something depending on the row you click (column always > 94), in tmux something is printed, for example
I searched the internet for the column 94 problem and found an interesting discussion that explains why this happens (the illustrious Mr. Dickey): Ncurses not reporting mouse movements after columns 94. Now, I have no knowledge of how UNIX consoles work, I only know 1/1000 of the escape sequences that make up the standard (the standards, from what I understood by trying to learn from many documents that I consulted starting from those on Mr. Dickey's site). What I understood is that I didn't understand a damn thing.
My question is: is there a possibility that in the FreeBSD virtual console the mouse can work beyond column 94? By modifying the /etc/ttys file, creating a special $HOME/.termcap or any other means or is this behavior typical of the FreeBSD virtual console?
What I understood is that xterm (based on every implementations) can generate different mouse response modes. In the javascript package I'm using, there is an undocumented setting to force how the mouse should work, by setting an environment variable containing a list of mouse protocols to enable and disable, but it seems that it doesn't work, whatever you sets the variable, the mouse is always recognized as 'X10' even if I force its disabling (probably either the enable/disable mechanism is not taken into account or this mode is set because the others would not work. I'm still trying to understand the javascript code).
In practice (if it can be useful) the environment variable that I set is the following:
Still in relation to the mouse, I would also like to know if it is possible to disable automatic text selection with the mouse buttons.
The real problem is that in xorg (xterm, xfce-terminal, etc) and in a remote console via ssh (windows terminal, putty, etc), everything seems to work. But in virtual terminal consoles (VT or ttyvN) the mouse stops working after column 94. I've also verified this with mc, htop and tmux and it does not work, but... in htop clicking after col 94 do something depending on the row you click (column always > 94), in tmux something is printed, for example
#x# but the three characters change based on row/column). For that reason I guess the console can handle the mouse over the 94th column. I don't normally use virtual consoles: I access my server remotely (ssh + putty or windows terminal), in the virtual machine I have installed a desktop environment.I searched the internet for the column 94 problem and found an interesting discussion that explains why this happens (the illustrious Mr. Dickey): Ncurses not reporting mouse movements after columns 94. Now, I have no knowledge of how UNIX consoles work, I only know 1/1000 of the escape sequences that make up the standard (the standards, from what I understood by trying to learn from many documents that I consulted starting from those on Mr. Dickey's site). What I understood is that I didn't understand a damn thing.
My question is: is there a possibility that in the FreeBSD virtual console the mouse can work beyond column 94? By modifying the /etc/ttys file, creating a special $HOME/.termcap or any other means or is this behavior typical of the FreeBSD virtual console?
What I understood is that xterm (based on every implementations) can generate different mouse response modes. In the javascript package I'm using, there is an undocumented setting to force how the mouse should work, by setting an environment variable containing a list of mouse protocols to enable and disable, but it seems that it doesn't work, whatever you sets the variable, the mouse is always recognized as 'X10' even if I force its disabling (probably either the enable/disable mechanism is not taken into account or this mode is set because the others would not work. I'm still trying to understand the javascript code).
In practice (if it can be useful) the environment variable that I set is the following:
Code:
export BLESSED_FORCE_MODES="SGRMOUSE=1,UTFMOUSE=1,VT200MOUSE=1,URXVTMOUSE=0,X10MOUSE=0,DECMOUSE=0,PTERMMOUSE=0,VT200HILITE=1,JSBTERMMOUSE=0,CELLMOTION=1,ALLMOTION=1,SENDFOCUS=1"Still in relation to the mouse, I would also like to know if it is possible to disable automatic text selection with the mouse buttons.