@Rowan-Sylvester-Bradley

I’m confused – If I do a Find-in-Files regex search for . on a big folder tree I get a box with status and a big fat CANCEL button. And, unlike some other programs with a similar cancel button, this one actually seems to work.

See for example Markdown is a simple way to format text …

@Joelbow

It’s great that your problem is solved, but if you’d provide more detail on the “special characters” in your macro that caused it to crash, we could think about it further, and maybe learn something we didn’t already know.

shortcuts.xml can be edited with Notepad++ as long as you don’t use the Shortcut Mapper functionality to change a shortcut key assignment at the same time (during the same run) as you make other (manual) edits to the file. If you make manual edits AND also use the Shortcut Mapper to make a change during the same run, Notepad++ will (in order to update the key-combo change), write out a new complete copy of shortcuts.xml from what is currently in memory–which will not include any manual edits to the file.

I would suggest you to double-check that you are selecting the proper file. Are you manually opening it from the File menu, or using any other method?

Did you try Google? See Python - RegEx for splitting text into sentences (sentence-tokenizing)

Ah, I closed npp and when i restarted it next time, line nos. were appearing.

I was not aware that a restart is required to make it work.

rawat

@Andrés-Zsögön

In the Shortcut Mapper, highlight what you want to remove the assignment from.
Press Modify.
In the dropdown box the top entry is “None”; choose that.
Press Apply
Press OK

Kinda clunky but it works (not saying the aren’t bugs at play here, just providing a workaround).

That makes sense, thank you.

“Expected” behaviour since a long time.

One part of the code for the visual representation is here in a n++ specific scintilla lexer:
https://github.com/notepad-plus-plus/notepad-plus-plus/blob/master/scintilla/lexers/LexSearchResult.cxx

and the search itsself is done in somewhere in the n++ code itself and then transfered to the search result window. In this protocol as far as I remember there is just one marker start/end per line.