Note the colored bits placed next to the scroll bar on the right. Those were created when I used the find command on one of my #defines. I think they are put there to mark all the 'hits' I had on the find.
This is a good feature, but the markers mean less when some remain after the find dialog box is closed. They then confuse with the next find command output.
I know this is a nit-picky little flaw, but on release I garontee (thanks Justin Wilson) that new users will complain. Now's the time to fix it.
It is never all the markers, just a random sampling.
This issue is tracked by the Arduino IDE developers here:
I just did some experimentation and didn't encounter that bug. Would you mind providing instructions I can follow to reproduce the problem of only some of the matches being marked?
In the above picture, a small black line appears to indicate the cursor position.
An orange vertical block apparently is telling me I have syntax errors (which are not real errors, this code compiles and runs).
Anyway, glad to know this is being worked on.
I also tend to get a bit mixed up between the different markers in the scroll bar. Mostly in my VS Code scrollbar due to all the false positives from the spell check extension I installed on top of the normal ones.
If you turn on compiler warnings in File > Preferences you'll see the compiler is also warning you about this:
C:\Users\per\Documents\Arduino\sketch_may18a\sketch_may18a.ino:1:25: warning: narrowing conversion of '-1' from 'int' to 'const char' inside { } [-Wnarrowing]
const char Murray[1] {-1};
^
