-
-
Notifications
You must be signed in to change notification settings - Fork 207
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
feat: fully support the "guicursor" option #1876
Comments
confirmed w/ NVIM v0.10.0 9765efb40f5 |
It's because we hardcode the cursor style in visual mode. It is a "fake" cursor that is shown through the highlight provider, not the cursor provider.
I'm not even sure if the highlight API allows for cursor-like highlights. |
This comment was marked as off-topic.
This comment was marked as off-topic.
@tmpm697 the primary cursor is the real cursor rendered in VSCode, which is actually the "primary selection" with 0 width. In vim visual mode, the selection and the cursor are two separate entities. To select the correct text, the vscode cursor is used for the selection, and a fake cursor is shown to represent the vim cursor. We keep track of user's cursor settings for the main cursor: vscode-neovim/src/cursor_manager.ts Line 132 in f7f8938
vscode-neovim/src/cursor_manager.ts Lines 156 to 170 in f7f8938
|
Currently, it's difficult to find a concise implementation method. "fake_cursor" is essentially just a special "highlight" without targeted handling logic in vscode. To fully support the "guicursor" option, we'd need to maintain a vscode decorator serving as the cursor, updating its color, shape, position, etc. |
Check the following:
Neovim version (nvim -v)
NVIM v0.9.4
Operating system/version
macos ventura 13.6.6
Describe the bug
I have this option:
vim.o.guicursor = "a:ver100"
, epxect all cursor shape of all modes will be|
but the visual/selecting mode still have block cursor shape.Steps To Reproduce
just have above option in neovim config
Expected Behavior
epxect all cursor shape of all modes will be
|
The text was updated successfully, but these errors were encountered: