Search++: A work in progress

[guy038]

Hello, @coises, @Lachlanmax and All,

Waoou ! This new 0.54 version of Search++ is almost perfect ! I do hope that @Lachlanmax will have the same feeling than me, regarding the Dark Mode displaying, that I don’t use personally !

• The Bookmarks and Show commands, in ICU mode, work correctly.

• The possible insertion of control chars, within the Find and Replace has gone away !

• The symbols, written on the different buttons, are much more intuitive and easily allow us to control what we’re doing. I particularly like the Open Documents scope and Documents in this view scope symbols !

• As implemented in the previous version, when focus is on Search++, a Ctrl + J action toggles from Jump to next match to Do not jump to next match. But now, it’s really more obvious to get the difference between the two symbols when looking at right of the Replace button !

---

One remark :

• For the Selection scope, the symbol does not really look like a true letter S, unlike the Marked Text scope, which clearly displays the symbol M !

Refer the snapshot, below, with the Whole document scope on left of Find button, the Selection symbol on left of the Count button and the Marked Text symbol on left of the Find all button :

The Selection scope seems less easy to identify , at first sight, isn’t it ?

May be, could you choose, for example, the 1F142 Unicode character which is the SQUARED LATIN CAPITAL LETTER S :   🅂  and, in the same way, the 1F13C character which is the he SQUARED LATIN CAPITAL LETTER M :   🄼  ?

To this purpose, refer to https://www.unicode.org/charts/PDF/U1F100.pdf

---

Now, a very simple bug to fix :

When the ICU is selected, if you try to do a simple Replace operation, Search++ displays the expected message Command not implemented and, of course, no replacement occurs.

Oddly, if you click on the Replace All button, the plugin displays the message Replaced xx matches in ... where xx represents the number of matches detected in current document ! But, luckily, no global replacement is performed, as well. I suppose that the identical message Command not implemented should be triggered, isn’t it ?

BTW, if the replacement process was allowed, in ICU mode, it seems that it would allow more than 9 back-references but would not accept any conditional replacement !

I also noted that the recursion feature is not allowed with the ICU regex engine !

Best Regards

guy038

P.S. :

• I tried to double-click on the font file Search++-Private-Symbols.otf and I was able to recognize all the symbols used by your plugin !

• In this version, in addition to the Search++-Private-Symbols.otf file, you also added a Search++.pdb file, which is quite large, indeed ! What is it used for ?

[Coises]

@guy038 said in Search++: A work in progress:

• The symbols, written on the different buttons, are much more intuitive and easily allow us to control what we’re doing. I particularly like the Open Documents scope and Documents in this view scope symbols !

• As implemented in the previous version, when focus is on Search++, a Ctrl + J action toggles from Jump to next match to Do not jump to next match. But now, it’s really more obvious to get the difference between the two symbols when looking at right of the Replace button !

Good! I was hoping these symbols would be more consistently easy to read across different systems. Thank you for confirming that it looks better on yours.

• For the Selection scope, the symbol does not really look like a true letter S, unlike the Marked Text scope, which clearly displays the symbol M !

I see your point. I’m not happy with using letters instead of graphic representations, but so far I have not been successful at inventing “pictures” of selected and marked text that render well as characters in a font. I will keep trying and, failing anything better, at least make a more identifiable “S” for selection.

Now, a very simple bug to fix :

When the ICU is selected, if you try to do a simple Replace operation, Search++ displays the expected message Command not implemented and, of course, no replacement occurs.

Oddly, if you click on the Replace All button, the plugin displays the message Replaced xx matches in ... where xx represents the number of matches detected in current document ! But, luckily, no global replacement is performed, as well. I suppose that the identical message Command not implemented should be triggered, isn’t it ?

Yes, it should show “Command not implemented.” I’ll fix that.

• In this version, in addition to the Search++-Private-Symbols.otf file, you also added a Search++.pdb file, which is quite large, indeed ! What is it used for ?

Visual Studio uses *.pdb files to support debugging. I included it in the x64 zip file by mistake. I’ve replaced the Search++‍-0.5.4-x64.zip artifact in the release with one that doesn’t contain that file. Thank you for catching that.

[guy038]

Hi, @coises and All,

Ah…, many thanks, in avance, for resolving bugs and trying to take into account my suggestions !

Regarding the Search++.pdb file, I can, of course, try to re-download the x64 archive. But can I, without any problem, simply delete this present file in my Search++ folder ?

BR

guy038

[Coises]

@guy038 said in Search++: A work in progress:

Regarding the Search++.pdb file, I can, of course, try to re-download the x64 archive. But can I, without any problem, simply delete this present file in the Search++ folder ?

Yes.

[guy038]

Hello, @coises and All,

Sorry to disturb you again, but would it be possible to, either :

• Increase the width of the caret

OR

• Allow, like in native N++, the modification of its width, in your Settings dialog

---

Personally, I use the value 3 in Caret Settings in Notepad++ and yours seems really tiny. So, it rather difficult to notice the caret location at first sight, in the Find dialog !

I must admit that I probably get used to this maximum value for the caret and that, now, any smaller size bothers me a bit !

Best Regards,

guy038

[Coises]

@guy038 said in Search++: A work in progress:

Sorry to disturb you again, but would it be possible to, either :

• Increase the width of the caret

OR

• Allow, like in native N++, the modification of its width, in your Settings dialog

I will add that to the list of things I copy from the the active document window when I initialize my Scintilla controls, and look for other similar settings (like the blink rate) that I missed. Not everything is simple to copy, but those are.

Thank you for pointing that out.

[guy038]

Hello, @coises and All,

I finally succeeded to get an almost exhaustive list of all the Unicode properties recognized by the ICU regex engine of the Search++ plugin !

As its file size is adbout 213 Kb, I’m about to share this simple text file, named ICU.txt, on my Drive Account

https://drive.google.com/file/d/15n8ttdX0hNxIazlRkToZn2XsINus5IOW/view?usp=sharing

Of course, this is my first attempt, which probably will need some modifications !

Best Regards,

guy038

[Coises]

@guy038 said in Search++: A work in progress:

I finally succeeded to get an almost exhaustive list of all the Unicode properties recognized by the ICU regex engine of the Search++ plugin !

[…]

https://drive.google.com/file/d/1litn6Ggjk-nRc8UOuxYS-5iO10_J-Z_2/view?usp=sharing

Edit to match updated quoted post: the link is now

https://drive.google.com/file/d/15n8ttdX0hNxIazlRkToZn2XsINus5IOW/view?usp=sharing

That clearly entailed a lot of work!

When I get closer to a “real” release, I will ask your permission to include some or all of that information as an appendix in the documentation for Search++.

[guy038]

Hi, @coises,

That’s really kind of you to ask for my permission.But, considering all the times you’ve listened to me, the least I can do is, of course, give you my full permission to use this file ;-))

---

Just note that I noticed, at the very end of the ICU.txt file, a small section that I used to verify if the \p{...} syntaxes were written correctly

As this part should not be part of the file, I modified the current file which, of course, changed the sharing link ! And I’ve just updated this link in my previous post !

Best Regards,

guy038

[guy038]

Hello, @coises and All,

Here is the second version of my list of all the Unicode properties, recognized by the ICU regex engine of the Search++ plugin !

I added 5 Unicode properties and some sections ( unsupported features, deprecated properties,… ) and I corrected a lot of mistakes !

In addition, although the ICU syntax is very flexible, I tried to adopt the same scheme throughout all sections of this file !

You can download this text file, named ICU.txt, from my Drive Account, at this location :

https://drive.google.com/file/d/1PAY5C2JO0q4-j8kfGKYs3VKarKn_xVa5/view?usp=sharing

Of course, I also deleted the previous version !

---

Now, one question regarding ICU

So far, you have chosen to disable replacements when using the ICU regular expression engine. What is that, exactly :

• Are you worried about a possible malfunction of that feature ?

• Are there any technical obstacles to implementing such a feature ?

• Do you need more time to learn about and/or implement this feature ?

• Or did you simply decide that it would never be used ?

Personally, I don’t see why this should be any more complicated than when using the Boost search engine when you click on the Regex button of your plugin !

Best Regards,

guy038