-
Notifications
You must be signed in to change notification settings - Fork 380
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
Add option to turn off selection cursor blink in input #1101
Comments
I figured out what selected field in theme.toml does, and it don't change cursor behavior |
I don't quite understand what you mean, can you record a gif? |
I see, but Yazi doesn’t add a blinking to the cursor. I think it largely depends on your terminal style/config - what terminal are you using? Is it the same with other terminals? My terminal (kitty) looks like : screenshot-000096.mp4 |
idk why, but wezterm draws blinking cursor in all yazi's input popups. But disabling blinking globally is not a great solution. Can it be changed in other way? |
And also, it seems like you also got some sort of blink, or i misunderstand it |
foot_blink.mp4Checked out foot, also got blinking in input fields. I mean is there a way to make cursor in input field completely constant? Maybe add settings group for cursor in theme.toml (it will be nice!) ? |
It is terminal "problem"/config. I'm on Debian 12 stable and I try with any terminal, but doesnt blink:
|
@og900aero i got cursor blink in kitty too... (zero config) kitty_blink.mp4 |
I'm going to lock this issue because it has been closed for 30 days. ⏳ |
Please describe the problem you're trying to solve
Search, find and other popups got cursor blink (or some sort of animation). I thought that it can be changed in theme.toml [input] -> selected field, but changing anything here does nothing to ui.
Would you be willing to contribute this feature?
Describe the solution you'd like
Add option to theme.toml that turn off cursor blink animation.
If it exist, add some guidelines for it in documentation
Additional context
No response
The text was updated successfully, but these errors were encountered: