Change colors in console window open after Find All in Current Document

Steven Haymes

To All,

When doing a Find All in Current Document, NPP opens a console window with all the lines in the active file that contain the search string. The foreground and background default style colors of the console window are the same as that of my custom theme in the edit window, but the foreground and background colors of the line numbers and found text are not. How can I change the foreground and background colors in this console window? It is not obvious in the Style Configurator.

Thanks,

Steve

Alan Kilborn

@Steven-Haymes

In Style Configurator, the last entry in the Language box is Search result where you can change some settings. Perhaps this will meet your need?

Alan Kilborn

Looking deeper…

Everything available in the Style Configurator for this makes sense except for Selected Line. By default it has a very dark blue Foreground colour and a bright yellow Background colour, but in practice I can’t seem to see these colors in the Find-result panel after doing some experimental searches and then some careting-around in the panel. Anyone have a different experience?

PeterJones

@Alan-Kilborn said:

Anyone have a different experience?

Nope, I don’t see that style have any affect in the search results window, either. Weird.

Maybe someone who knows where in the codebase the search-results picks its styles, and can look up whether the code ever actually calls that style.

guy038

Hi, @steven-haymes, @alan-kilborn, @peterjones, and All,

The last N++ version which correctly handles the Selected Line style, of the pseudo-language Search Result, seems to be the v5.7 release ! With the next release, v5.8, the highlighting, when double-clicking, in the Find Result panel, does not work anymore -((

To clearly see the difference, just download a portable version 32-bits, of the v.5.7 release, from :

https://notepad-plus-plus.org/download/v5.7.html

BTW, there’s something weird about this transition : After the v5.7 release, two Release Candidate ( v5.7.1 RC and v5.7.1 RC2 ) were finally skipped, in order to, directly, move to the v5.8 release !

But, when you have a look to the fixed regressions, in v5.7.1 RC2, from v5.7.1 RC ( Refer below )

https://notepad-plus-plus.org/news/notepad-v5.7.1-rc2.html

You’ll notice the line :

3. Fix Lexer SearchResult syntax highlighting bug.

And probably, problem then arose !

Here are, below, the new features and fixed bugs of the 4 releases v5.7, v5.7.1 RC, v5.7.1 RC2 and v5.8 , in that order :

~~~~~~~~~~~~~~ v5.7 Official Release ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

https://notepad-plus-plus.org/download/v5.7.html

Notepad++ v5.7 new features and fixed bugs (from v5.6.8)

     1. Upgrade Scintilla to version 2.12.
     2. Add "Inverse bookmark" feature.
     3. Add NPPM_SAVECURRENTFILEAS message.
     4. Fix premature deallocation bug for import UDL.
     5. Add import/export User Defined Language features.
     6. File detection : Switch to modified or deleted file while user is asked to reload or keep the file.
     7. Fix closing several detected non-existing files bug.  
     8. Fix language switching to English not working bug.
     9. Reduce PostIt/FullScreen restore button size.
    10. Fix PostIt wrong restore button position after toggling off fullScreen mode.
    11. Fix crashes on new 11 character long UDL names bug.
    12. Fix "Save all" inconsistent icon state on toolbar.
    13. Add new keywords of HTML 5 and css.


~~~~~~~~~~~~~~ SKIPPED version ~~~~~~~~~~~~~~ SKIPPED version ~~~~~~~~~~~~~~ SKIPPED version ~~~~~~~~~~~~~~ SKIPPED version ~~~~~~~~~~~~~~

https://notepad-plus-plus.org/news/notepad-5.7.1-release-candidate.html

Here are Notepad++ v5.7.1 RC new features and fixed bugs (from v5.7)

     1. Upgrade Scintilla to version 2.20.
     2. Fix Unicode file corrupted on saving bug (the buffer alignment issue).
     3. Fix DBCS encodings file saving corruption bug.
     4. Fix file containing NULL character loading bug.
     5. Fix php syntax highlighting bug.
     6. Fix Shortcut Mapper inconsistence issue after deleting a macro or an user command.
     7. Add 2 line wrap methods (default plus aligned and indent).
     8. Add 2 menu commands : "Modify Shortcut/Delete Macro" and  "Modify Shortcut/Delete Command".
     9. Add "Modify" and "Delete" buttons on Shortcut mapper dialog.
    10. Add macro new ability to record search and replace actions.
    11. Fix SaveSession bug.
    12. Remove characters count feature from the status bar due to its performance issue with UTF8 file.
    13. Fix crash issue due to themes switching.
    14. Make folding margin hidable.
    15. Add NPPM_GETCURRENTNATIVELANGENCODING message (to get the current native language enconding).
    16. Change editing settings saving behaviour : one set of settings are applied in 2 scintilla controls (except zoom).


~~~~~~~~~~~~~~ SKIPPED version ~~~~~~~~~~~~~~ SKIPPED version ~~~~~~~~~~~~~~ SKIPPED version ~~~~~~~~~~~~~~ SKIPPED version ~~~~~~~~~~~~~~

https://notepad-plus-plus.org/news/notepad-v5.7.1-rc2.html

Notepad++ v5.7.1 RC2 Enhancement and bug fixed (from v5.7)

    1. Update Scintilla to v2.21.
    2. Fix a vulnerability issue: Load ScinLexer.dll with its full path to avoid hijack.
    3. Fix dragging undocked window performance issue while using Vista Aero UI style.
    4. Fix large file truncated after loading problem.
    5. Improve file loading performance.

Notepad v5.7.1 RC2 Regressions fixed (from v5.7.1 RC)

    1. Fix "Select and Find Next" and "Count" regressions.
    2. Fix the menu items settings non-memorized regression.
~~> 3. Fix Lexer SearchResult syntax highlighting bug.        <~~~~~~~~~~~~
    4. Fix macro recoding for find in files regression.
    5. Fix html/xml/php folding disappeared problem.
    6. Fix "#if 1 //" making Notepad++ crash issue.


~~~~~~~~~~~~~~ v5.8 Official Release ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

https://notepad-plus-plus.org/download/v5.8.html

Notepad++ v5.8 new features and fixed bugs (from v5.7)

     1. Upgrade Scintilla to version 2.21.
     2. Fix a vulnerability issue: Load ScinLexer.dll with its full path to avoid hijack.
     3. Fix Unicode file corrupted on saving bug (the buffer alignment issue).
     4. Fix DBCS encodings file saving corruption bug.
     5. Fix file containing NULL character loading bug.
     6. Fix php syntax highlighting bug.
     7. Fix dragging undocked window performance issue while using Vista/Windows7 Aero UI style.
     8. Fix large file truncated after loading problem.
     9. Improve file loading performance.
    10. Fix Shortcut Mapper inconsistence issue after deleting a macro or an user command.
    11. Add 2 line wrap methods (default plus aligned and indent).
    12. Add 2 menu commands : "Modify Shortcut/Delete Macro" and  "Modify Shortcut/Delete Command".
    13. Add "Modify" and "Delete" buttons on Shortcut mapper dialog.
    14. Add macro new ability to record search and replace actions.
    15. Fix SaveSession bug.
    16. Remove characters count feature from the status bar due to its performance issue with UTF8 file.
    17. Fix crash issue due to themes switching.
    18. Make folding margin hidable.
    19. Add NPPM_GETCURRENTNATIVELANGENCODING, NPPM_ALLOCATECMDID and NPPM_ALLOCATEMARKER message (to get the current native language enconding).
    20. Change editing settings saving behaviour : one set of settings are applied in 2 scintilla controls (except zoom).
    21. Add Statistics feature which is accessible from the menu command "Summary..." (under menu "View") and the 2nd zone of statusbar (double click).

BR

guy038

P.S. :

On my first N++ v4.9.2 release, the highlighting, in the find result panel, was reversed, with foreground in light yellow and bold font and background in true blue !

Alan Kilborn

@guy038 said:

last N++ version which correctly handles the Selected Line style, of the pseudo-language Search Result, seem to be the v5.7 release ! With the next release, v5.8, the highlighting, when double-clicking, in the Find Result panel, does not work

Of course you are correct. You win some sort of detective award for this effort. :)

It is good to know the history, but I find that with this change from v7.5.7:

Make caret line always visible on click from Finder panel.

that the Selected Line style really isn’t that necessary anyway. What do you think?

Steven Haymes

@Alan-Kilborn,

Thanks,

Style Configurator -> Language -> Search results did the trick.

One thing that I am curious about is if highlight overlays are cumulative? For example, if my current line is RGB 50 50 50 for a dark gray and my selected text is RGB 100 100 100 for a less dark gray, it appears that in the area of overlap, the line is actually lighter than 100 100 100 and more like 150 150 150 for a medium gray.

Has anyone seen this?

Thanks,

Steve

PeterJones

@Alan-Kilborn said:

the Selected Line style really isn’t that necessary anyway. What do you think?

If none of us power-users had noticed that particular highlighting was missing since v5.8 (or at least it hadn’t bothered us enough to say anything), then it’s probably not necessary. :-)

PeterJones

@Steven-Haymes said:

it appears that in the area of overlap, the line is actually lighter than 100 100 100 and more like 150 150 150 for a medium gray.

Yeah, it wouldn’t surprise me if it did apply some combo of the various highlight overlays – I don’t know whether it’s a linear combo, though. (Obviously, at some point, it stops, since it won’t go over 255 255 255… :-))

But if you told me that those two grays were different, I wouldn’t disagree with you. (My greyscale distinguishing isn’t great… and I’m often using NPP over a remote desktop connection, and colors don’t make it through the tunnel unaffected.)

guy038

Hi, @steven-haymes, @alan-kilborn, @peterjones, and All,

@peterjones

I did notice that difference, a long time ago. But, both, I’ve been able to live, with that regression, up to now and I was not courageous enough to post an issue, on GitHub ;-))

@alan-kilborn

You’re right ! Current line, in the Find Result panel, has a light background color, anyway ! This gives me an idea for a possible work-around, in order to easily localize the double-clicked line :-))

Just change the background color of the Current line background color style, of the pseudo-language Search result, to a darker color ;-)). For instance, you could choose, in a RGB notation :

A Violet color : 255,160,255
A Blue color : 128,160,255
A Yellow color : 255,255,96

Of course, doing so, prevents you from changing the foreground color of text. However, I verified that, even if you open successive Find result panels, by right-clicking and choosing the Find results in these found results option, the current line is still highlighted, with this darker color !

Cheers,

guy038

Alan Kilborn

@guy038 said:

idea for a possible work-around, in order to easily localize the double-clicked line

Can you elaborate more on how this is advantageous? To me it just sounds like changing out one color for another, with no “improvement” in functionality. Clearly I am missing the point…it happens. :)

guy038

Hi, @alan-kilborn and All,

With the v4.9.2 release, by default :

With the v5.7 Unicode release, by default :

With the last v7.7.1 Unicode release, by default :

Obviously, it easier to localize the double-clicked line, of the Find Result panel, in the first two pictures than in the third one ;-))

Indeed, my work-around is not complicated at all ! I just made the current line background color darker, in order to simulate the selected line style, which does not work, anymore !

So, for instance, with a darker yellow, we get the 4th picture, below, which is better visible than in the 3th picture above ;-))

With the last v7.7.1 Unicode release, after modification of the background color of Current line background style of the Search result language :

Cheers,

guy038

Alan Kilborn

@guy038

Oh, OK, it IS just a color change. I thought you had some magic whereby you achieved some additional functionality. :)

Thanks for clarifying, and the images.

Steven Haymes

@guy038

“Indeed, my work-around is not complicated at all ! I just made the current line background color darker, in order to simulate the selected line style, which does not work, anymore !”

I suspected that the selected line style was not working, thanks! My custom theme has a black background, so I already achieved the same result as you by going lighter instead.

Steve