What are the blue highlighted lines?

[jackhab]

See attached picture, please.
Will somebody explain to me what is the meaning of this blue background I got from time to time? And how do I get rid of it?

[attachment deleted by admin]

[Ceniza]

That background highlights the current line. To disable it, go to Settings -> Editor -> General Settings. In there, uncheck the option Highlight line under caret.

[jens]

That background highlights the current line. To disable it, go to Settings -> Editor -> General Settings. In there, uncheck the option Highlight line under caret.

Not the blue ones.

They appear if browsemarks style is set to browse marks in lines where a browse-mark is set.

I think it appears with new scintilla branch. Browsmarks might interfere with either changebar-margin or moder-style indicators, or something was forgotten when updating to new scintilla.

Anyway, I will look into it.

[jens]

More precisely (after some research).
This happens for me, if I have browsemarks set ( three dots) and then disable browsemarks, for the browsemarks I had.

Or if I enable browsemarks (they have to be disabled of course) and then enable them. After a restart of C::B with browsemarks enabled, everything is ok (three dots).

[jackhab]

I don't even touch browsemarks. I open some settings dialog and close it even without modifying the settings and then bang - I have a couple of these. Unfortunately it's so inconsistent I can't reproduce it.

[jens]

I don't even touch browsemarks. I open some settings dialog and close it even without modifying the settings and then bang - I have a couple of these. Unfortunately it's so inconsistent I can't reproduce it.

By default browsemarks are set, if you press left mouse-key for more than 200 ms in a line.
The browsemarks are the three dots in the left margin.

If you have opened "Settings -> Editor" and left it with "OK" the bug appears, because the editor does not take care of the margin settings of plugins.
All lines that contain browsemarks wil become blue.

I will commit a fix for this issue, if I have tested it enough.