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
cells show symbol occurrence highlighting when in command mode #173971
Comments
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.75.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding! |
Upgraded to |
This has bugged me too, do you know if there is a way to clear these @rebornix ? |
@roblourens the symbol/word highlight is not cleared when the editor loses focus, which is expected in a normal text editor but not in a cell editor I guess. We need to check if the contrib allows us to clear/hide them and reenable when the editor gains focus. I'll check. |
For what it's worth, I would personally expect it to be cleared in both cases because the highlights are meaningless without keyboard focus. |
It makes good sense to me to disable this in notebook. Changing the behavior in Monaco might be breaking. We can see how to expose enable/disable functionalities from the word highlighter contrib. |
Thank you both. Jupyter notebooks + VS Code editor is overall a delightful and polished UX – well done. |
Environment data
1.73.1
1.75.0
v2022.9.1303220346
v2022.18.2
Mac
3.10
Docker
Local
Expected behaviour
VS Code provides occurrence highlighting of the symbol currently under the visible cursor. (Enabled by default as setting
editor.occurrencesHighlight
). This is useful when a cell is in edit mode.When the cursor is not visible because a cell is in command mode, these highlights are no longer relevant or meaningful and should be hidden with the cursor.
Actual behaviour
Occurrence highlighting persists even in command mode, leading to highlights which confusingly look like find/search results.
Steps to reproduce:
The text was updated successfully, but these errors were encountered: