-
Notifications
You must be signed in to change notification settings - Fork 12
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
Cursor not visible when moving #3
Comments
I don't use alacritty so forgive me if things come off as naive, still looking into things - but if I just download alacritty and fire up a new session of it with nothing other than import:
- /path/to/dracula.yml
window:
title: "Dracula Test Stuff"
dynamic_title: false I don't seem to have any particular issue with the cursor, gives the standout effect as intended. This sounds like something being an issue with the terminal emulator/how its handling something. What is your
is what's working for me, I imagine the could you try running: echo `tput smso`standout`tput rmso` and show what it is? |
It appears to be some sort of conflict with the "dracula-pro" alacritty theme. I need to further investigate. The cursor behaviour seems to be different depending what cursor foreground is set to in |
Strange; for reference, on an unknown token, still works for me as well: ... so does indeed seem to be an issue with the difference between the pro/non pro version. To confirm, if you try replacing with the non-pro values: colors:
primary:
background: '0x282a36'
foreground: '0xf8f8f2'
cursor:
text: CellBackground
cursor: CellForeground
... does it then work for you for the above scenario? |
Actually this does not work for me either. I am seeing the same issue except now I do not see the cursor appear on any tokens. |
D: lol OK, so that's not it. It is hard for me to play with/look much into without having Pro, so apologies; I guess as a more general sanity test, if you switch to using entirely the non-pro theme for alacritty, https://github.com/dracula/alacritty/blob/master/INSTALL.md#install, does it then work? Trying to figure out if its a Dracula pro issue or an alacritty issue (am leaning towards the former, since it works on my barebones alacritty, but then again, i'm using
|
It is kind of a bizarre situation but I have tried reducing my alacritty config to default theme and disabling all zsh plugins except for this one and I cannot get around the
As mentioned above my term is |
Oh shoot, my bad, missed that in your screenshot above, right, thanks. I can try messing with my TERM value in a little bit when I'm near my computer again; will check my alacrity release too (originally grabbed just whatever is in homebrew currently) |
As a side note I tried it in Terminology terminal and it appears to work fine there. Maybe its an upstream Alacritty issue once we validate versions |
Mine is:
... so echo -e "\e[7m is this standout? \e[27m"
# and/or
echo `tput smso`standout`tput rmso` both result in standout coloring for you, so I agree, its something with how the colors are interacting that is prevneting it, since your setup definitely supports ... and using |
I just built the latest upstream git rev-parse HEAD
78795522e93a6010e07da524256c0339720e6d1c and then sudo tic -xe alacritty,alacritty-direct extra/alacritty.info
exec zsh
export TERM=alacritty-direct ... and even still using the non-pro dracula colors (and that barebones config in the beginning comment) works properly |
Well doh -_- I never uploaded the cursor line to the themes file...: # ....
ZSH_HIGHLIGHT_STYLES[cursor]='standout' |
I merged the code (and it auto-closed this bc the cross-reference); I'll wait to close this until you confirm that getting the latest fixes the issue. Thanks! (And sorry about all this) |
Thankyou again for the responsiveness to this obscure issue. I don't think you should need to define that since it gets inherited with that value in https://github.com/zsh-users/zsh-syntax-highlighting/blob/dffe304567c86f06bf1be0fce200077504e79783/highlighters/cursor/cursor-highlighter.zsh#L32 I need to get to the bottom of this issue with standout but I have been able to programmatically reproduce it under certain colors. on=$(tput smso)"clear"`fb=3;r=255;g=85;b=85;printf '\e[0;%s8;2;%s;%s;%sm ON ' "$fb" "$r" "$g" "$b"`$(tput rmso)$(tput sgr0)
off=clear`fb=3;r=255;g=85;b=85;printf '\e[0;%s8;2;%s;%s;%sm OFF ' "$fb" "$r" "$g" "$b"`$(tput sgr0)
echo $off $on I am replicating the token not found color to demonstrate the standout is making no difference here |
Hmph. Can you post the output of your current infocmp alacritty-direct for comparison, too? Also, you're not also using tmux, right? |
Looked some more into this last night and this morning, and interestingly enough this really old issue seems to be exactly what's going on, right?:
... but that was since covered; recent issues discuss things like
so maybe alacritty is doing something bad based on the Dracula Pro colors? But if that was the case, I would have figured that when you switched to using the non-pro configuration for alacritty, things would have worked fine |
Not using tmux or screen
That issue looks like a similar problem although the reversal appears to only be disabled under certain color combinations. Like the contrasting issue you referenced. What happens when you run the above snippet? |
alacritty/alacritty#4564 seems to be it |
Thanks for digging. We are safe to close this since it is an implementation issue in the terminal. |
OK - sorry to hear things aren't working for you:\ BTW - If I ever get around to buying pro (no hate, just not really for me) I'll look back into this when I actually have the colors and am able to make a compliant set of "pro" versions. |
I have the same issue with cursor in tilix (in gnome term too, just for check). Setting |
Describe the Issue
I can not see the cursor when activating this theme. I am using Alacritty with the Dracula color scheme.
Zinit is my ZSH plugin manager
Expected behavior
I should be able to see the cursor when moving it from character to character.
Screenshots
See comment below
Additional context
My workaround is to modify the cursor highlight style.
The text was updated successfully, but these errors were encountered: