-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Spurious markers near the vertical scroll bars for smart highlighting #123
Comments
It seems to be a bug. Can you please check with latest release |
Looks to be related to specific document content. Tested some random files in the same session. The toml file content for reference: Link as the content gets mangled |
I could reproduce the issue!
|
Please check the latest release! |
@sieukrem Here are some of my findings:
Since I prefer thinner markers, for now the best solution for me is to just uncheck indicator 9 Would you mind sharing any documents explaining what the different indicators are and what they do? |
Describe the bug
When opening a large document vertical scrollbars show locations of highlighted words, even though I have not highlighted anything yet
To Reproduce
This happens randomly for me and I don't have an exact way to reproduce this, but whenever it does happen the steps mentioned above will produce it. I also usually have a large number of tabs open, although I am not sure if this is relevant.
Expected behavior
The markers next to the vertical scrollbar should only appear when I highlight words, and should disappear when I unhighlight them.
Screenshots
This is when I just open this large document.
I do not highlight any word, but just scroll down clicking and dragging the scroll bar
I highlight a frequently occurring word
I unhighlight the frequently occuring word
Is this a bug or is there a setting I need to change? I only use the jN plugin for the smart highlighting feature so I don't know any details about the plugin settings. I have kept everything at their default.
Environment
The text was updated successfully, but these errors were encountered: