-
Notifications
You must be signed in to change notification settings - Fork 266
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
How to change the cursor style to vertical line #781
Comments
Maybe someone in the |
I don't know how to use IRC (shame on me) and nobody seems to respond there, but that's not the point here. Is this possible? Like maybe just change some source code real fast and that's all? |
I think you mean vertical line, and no, it's not possible - there's no special handling of the cursor, it's rendered like all the text on the screen but with a special fg/bg color (the UI_STYLE_CURSOR value) so it fills the entire area of a single character (giving it the block 'style'). |
@3dc1d3 there a small patch in #406 (comment) than can give you vertical line (called |
Thanks I tried the patch and sadly that is not what i wanted. i wanted the cursor to be '|' not a block. I guess @3dc1d3 is right and i just have to live with it ._. |
@Theamazingwaffle What you are looking for is cursor shapes. But their handling is terminal-dependent. So any solution to your problem would be terminal-dependent. See for example, the different solutions to achieve this in vim for different terminals https://stackoverflow.com/questions/6488683/how-do-i-change-the-vim-cursor-in-insert-normal-mode It also relies on hooks triggered when entering/leaving insert mode. AFAICT, |
Cursor shape should be beam in insert mode and block in normal mode by default. I have this working in vim, lvim, nvim, and emacs with evil mode. |
The title.
Pls i'm crying, i tried reading some of the source code but i found just UI_STYLE_CURSOR and i have no idea what it does or how to change it so i don't break vis. Please help!
The text was updated successfully, but these errors were encountered: