@t-md Try the Language -> Define Your Language menu item. There is a link there to some documentation.

lol yea
I wasn’t aware that version 7.4 had it :)

Thanks Scott - that’s exactly like what I was looking for.

Unfortunately, it appears to crash when I open new docs :(

@guy038 said:

I’ve just noticed one bug. Luckily, after checking on official versions, that’s NOT due to your version !

I agree with your findings. The trouble seems to come from this section of the source code:

CharacterRange cr = (*_ppEditView)->getSelection(); //The search "zone" is relative to the selection, so search happens 'outside' int startPosition = cr.cpMax; int endPosition = docLength; if (pOptions->_whichDirection == DIR_UP) { //When searching upwards, start is the lower part, end the upper, for backwards search startPosition = cr.cpMax - 1; endPosition = 0; }

The line causing the trouble is startPosition = cr.cpMax - 1;

When the caret is here (at the position marked by the vertical bar): abcabcabcabcABC|abcabc and the backwards search for “abc” (without regard to case) is invoked, the -1 in the line above is what causes the search to begin at this position: abcabcabcabcAB|Cabcabc instead of at the correct starting point. Thus, the first match that is found is the last “abc” just before “ABC” (as @guy038 indicated), instead of “ABC”. This supposes that Scintilla’s searchInTarget() function (called later than the above snippet of code) won’t find matches that begin inside the specified range and extend outside the range.

Unfortunately, I don’t see an easy fix to this. If the line is changed to be startPosition = cr.cpMax; then “ABC” is correctly found as the first backward-search match, but repeated presses of the <<Find (my N++ build) or Find Next (real N++ 7.5) button will not move the caret, i.e., it will be stuck on “ABC” forever, instead of finding each preceding “abc” match in turn.

I’m on Windows 10 by the way. I had done all these steps, however I was moving the dll into the 32 bit ++ dir. (didn’t realize I still had 32 bit ++ installed, I still should have known to be in Program files and not the (86) dir). Ok thats done, and restarted notepad ++., it didn’t work untill I installed a dictionary…makes sense.
currently it is Using the Hurspell library as opposed to Aspell.
Which is better?

I’d like to add in other plugins, is there a good site which has all the 64 bit plugins?

I also do not have the plugin manager, where can I find this?

Thanks Much

Many thanks Scott.
I should have glue on my eyes :)
It’s OK !

thx
I had version 7.3.3 (not sure why didn’t update, probably firewall block it )

with 7.5 works fine

@guy038 said:

Very easy, indeed ! Just check the Wrap around option, in the Find / Replace / Mark dialog

Oh my… really easy. I thought Wrap around would mean search over multiple lines (wrap around line ending). Thanks a lot!

http://imgur.com/a/UnZQM

Hello, @yasser-hhalil and @scott-sumner,

Sorry, I’m not very reactive, cause I’m on holidays, in North Brittany, with my two sisters and their husbands. What to say ? We make a cure of seafood : cockles, periwinkles, clams, lobsters, crabs and even octopus ! To sum up : the Paradise ;-))Since one week, weather was quite fine, here, but today it was raining. So, I’m back to N++ and the Community, for a while !!

Ah, @scott-sumner, very clever regex, found by Alin Purcaru, on Stackoverflow site !

To complete this topic, let’s suppose we want to find all lines with the five first-names : jack, james, jason, jules and Joe

Here are, below, four regexes, from the more restrictive behaviour to the less restrictive behaviour :

In regex A, rhe five first-names must be true words, in the exact lower case

In regex B, rhe five first-names must be true words, whatever their case

In regex C, rhe five first-names may be glued in bigger words, but with their exact lower case

In regex D, rhe five first-names may be glued in bigger words, whatever their case

So :

Regex A = (?-is)^(?=.*\bjack\b)(?=.*\bjames\b)(?=.*\bjason\b)(?=.*\bjules\b)(?=.*\bjoe\b).*

Regex B = (?i-s)^(?=.*\bjack\b)(?=.*\bjames\b)(?=.*\bjason\b)(?=.*\bjules\b)(?=.*\bjoe\b).*

Regex C = (?-is)^(?=.*jack)(?=.*james)(?=.*jason)(?=.*jules)(?=.*joe).*

Regex D = (?i-s)^(?=.*jack)(?=.*james)(?=.*jason)(?=.*jules)(?=.*joe).*

Notes :

As usual, the Regular expression search mode must be checked !

The initial modifiers force the search to be sensitive / insensitive ( -i / i ) to case, and also means that dot matches a single standard character only ( -s )

The ^ assertion, stands for the location beginning of line, where starts the test of the following features ( look-arounds )

Each form (?.*......) is a positive look-around, a condition which must be verified to get an overall match

If all conditions are true, the final regex is simply ^.*, so all contents of the line, from its beginning

Then, if you copy/paste the following lines, in a new tab :

01 james 02 jason 03 joe 04 james and jack 05 jason and jules 06 jack, jason and joe 07 peter, joe, jack, james and jules 08 peter, jack, james, jason, jules and joe 09 james, joe, jason, jules, jack and margaret 10 peter, jules, james, jack, jason, joe and margaret 11 joe, jules, jason, james and jack 12 jAMes 13 jASon 14 jOE 15 jAMes and JAck 16 jASon and JUles 17 jACk, jASOn and joe 18 pETer, JOE, jack, jaMEs and JUles 19 pETer, JACk, james, JAson, jULes and joe 20 jAMes, JOE, jason, jULes, jaCK and margaret 21 pETer, JULes, james, Jack, jASon, jOE and margaret 22 jOE, juLES, jason, jAMes and Jack 23 james 24 jason 25 joe 26 james and jack 27 jason and jules 28 jack, jason and joe 29 peter, 12joe34, jack, 56james78 and jules 30 peter, 12jack34, james, 56jason78, jules and joe 31 james, 12joe34, jason, 56jules78, jack and margaret 32 peter, 12jules34, james, 56jack78, jason, joe and margaret 33 joe, 12jules34, jason, 56james78 and jack 34 jAMes 35 jASon 36 jOE 37 jAMes and 12jack34 38 jASon and jules 39 jACk, 12jASOn34 and joe 40 pETer, 12JOE34, jack, 56jaMEs78 and JUles 41 pETer, 12JACk34, james, 56JAson78, jULes and 90joe12 42 jAMes, 12JOE34, jason, 56jULes78, jaCK and margaret 43 pETer, 12JULes34, james, 56Jack78, jASon, 90joe12 and margaret 44 jOE, 12juLES34, jason, 56jAMes78 and 90Jack12

You’ll easily notice that :

Regex A matches lines from 8 to 11

Regex B matches lines from 8 to 11 and from 19 to 22

Regex C matches lines from 8 to 11 and from 30 to 33

Regex D matches lines from 8 to 11, from 19 to 22, from 30 to 33 and from 41 to 44

Now, from an already saved file, once you’ve got the results, in the Find Result panel, after clicking on the Find All in Current Document button, using one of regexes, above, you may, also, search for each individual first-name :

Right-click in the Find result panel

Select the Find in this finder… option

Now, in the new Find in finder dialog :

Type a first-name, for instance jack, in the Find what: zone

Check the Search only on found lines option

Uncheck the two options Match whole word only and Match case

Select, if necessary, the Normal search mode

Click on the Find all button

=> A new Find resul tab is created and displays any occurrence of the string jack, found in the lines of the Find result panel, only !

Repeat these steps, changing for an other first-name, to get 5 Find resul tabs, all using the Line Filter Mode of search !

IMPORTANT : If the Find result panel contains results, from a non-saved file ( with new # name ), the context option Find in this filder… does NOT seem to work ! I’ll add a post to @don-ho, to that purpose, very soon !

Best Regards,

guy038

A key point that I missed–but it worked anyway because it is the default option–is to check the Search only in found lines checkbox in the two Find in finder searches above. Otherwise, ALL LINES of the files hit in the prior searches get examined in subsequent searches, instead of only the lines that were hit earlier.

Imgur