-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v2] Can't change cursor #2248
Comments
Same issue different platform
~/.hyper.js contents
|
@PerStirpes @moso This is definitely a bug in version 2.0.3 If you want to use BEAM I recommend to go back to the stable version. |
@mapeso Yeah, I'm staying on 1.4.7 for the time being. |
@albinekb "BEAM" works well mac, windows and linux (check in 3). The only problem is that it has to be in the stable version (1.4.8) we can rule out that it is an issue related to the operating system 😄 |
Same here with Hyper v2.0.4 on Arch Linux. |
If you use the ZSH shell, a workaround is to use the ZSH line editor, then you can have whatever cursor you want. It is pretty easy to setup a blinking i-beam. Below at the bottom of your .zshrc would work. # zle config
bindkey -v # vi mode
export KEYTIMEOUT=1 # mode change timeout = 0.1sec
function zle-keymap-select zle-line-init
{
# change cursor shape in xterm
case $KEYMAP in
vicmd) echo -e -n "\x1b[\x32 q";; # block cursor
viins|main) echo -e -n "\x1b[\x35 q";; # blinking line cursor
esac
zle reset-prompt
zle -R
}
zle -N zle-line-init
zle -N zle-keymap-select
|
Just had some time to dig in. In the code term.js line 43, xterm module (version 2.9.2) does not accept |
I just encountered this with hyper v2 as wel; i cannot change the cursor type to anything but the default block style cursor. |
cursor-node
is a deprecated CSS class. But as this is reproducable without plugins, I guess it's irrelevantIssue
Even though it's stated with caps in my
hyper.js
config that I wantBEAM
as cursor, I still get the default block.Also related:
cursorBlink: 'true'
doesn't work either. Want me to submit a separate issue?The text was updated successfully, but these errors were encountered: