You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When changing the cursor style in the terminal (f.e.: echo -e -n "\x1b[3 q" for blinking-underline)
and running tcell, it is changed back to the (default) blinking block.
Steps to reproduce:
execute echo -e -n "\x1b[3 q" to change the cursor style in terminal
back in the terminal you'll noticed that the style is changed back to the default one.
This happens since commit 761abf6
It's probably because of the default value of 0 for cursorStyle in tScreen.
I guess to fix this it would be needed to get the current setting when tcell is starting and assigning it to cursorStyle. No clue if/how that is possible though.
There is no way (that I am aware of) to query the existing cursor style. So we can't save and restore it.
One thing we could do is conditionalize the "restoring" of the cursor style upon whether an application changes it or not.
If this bothers you greatly, you might see if your terminal emulator can support changing the "default". The value 0 is the "default" -- so terminals should restore the cursor to whatever the user preference for the default is.
Hi @gdamore
thanks for your quick reply. I guess setting the default style is the terminal itself is the way to go indeed.
Just tried it with xfce4-terminal and it works fine that way.
When changing the cursor style in the terminal (f.e.:
echo -e -n "\x1b[3 q"
for blinking-underline)and running tcell, it is changed back to the (default) blinking block.
Steps to reproduce:
echo -e -n "\x1b[3 q"
to change the cursor style in terminalThis happens since commit 761abf6
It's probably because of the default value of 0 for
cursorStyle
intScreen
.I guess to fix this it would be needed to get the current setting when tcell is starting and assigning it to
cursorStyle
. No clue if/how that is possible though.ref: moson-mo/pacseek#19
The text was updated successfully, but these errors were encountered: