Hello Yusuf and Gerdb42,

Gerdb42, I think that, annoyed about waiting 3 minutes to correct your post, your just omit the 3 groups to re-arrange the date :-))

So, Yusuf, the correct Gerdb42 S/R is, of course :

SEARCH : (\d{2})/(\d{2})/(\d{2})

REPLACE : \2/\1/20\3

Cheers,

guy038

P.S. :

Oh ! Thinking about the 2000’s years, here is an other solution :

SEARCH : (\d{2})/(\d{2})/(([0-4])\d|[5-9]\d)

REPLACE : \2/\1/(?{4}20:19)\3

So, supposing the year, written with TWO digits :

If the year is between the 00 and 49 values, we rewrite the string 20, followed by the year value

If the year is between the 50 and 99 values, we rewrite the string 19, followed by the year value

For instance, the two dates :

12/15/49 01/15/50

would be changed into :

15/12/2049 15/01/1950

Notepad++ is very tightly integrated with Win32 API. The classic windows look and feel is big part of its appeal (at least for me).
To port the same logic to a different GUI API (Linux GTK/QT/other or Mac whatever) probably at least 50% of the code will need to be rewritten. It could be a great product but it will not be Notepad++.
Most users are happy with current Win32 version and will not give it up so multiple versions will need to be maintained.
Most plugins will need to be adapted and maintain 2 versions. Most plugins developers will not (or could not) do it.

And in any case, if a porting effort would resume, a Linux port should have higher priority than a Mac port.

Money always helps but establishing pay model for existing free product is difficult.
A VERY big donation for independent developer(s) to start working on it full time for a year or so is probably the only way to make it happen.

I’m guessing the UDL was developed by someone who wanted something to highlight unsupported file types in a manner that the average person can make use of. Without it, you would have to write a lexer for Scintilla, and not many NPP users are going to do that.

I wish the UDL was more powerful (supporting regex in some ways, for example), but it offers a decent set of options for highlighting many types of “non-standard” files. I have certainly put it to good use–I have 13 UDL file types. :-)

I’m afraid that your desire can only be met by someone who shares that desire to a great degree and who has the ability to write an NPP plugin that will fulfill that desire.

Hello, MacGyver27 and All

Thinking to your problem, I’ve just imagined a particular search/replacement, that changes the case of each letter, of the replacement word, ACCORDINGLY TO the case of each corresponding letter, in the searched word :-)))

Hypotheses :

The searched and replacement words are supposed made of any word character. That is to say that they may contain possible digit characters and/or any underscore symbol as, for instance, the words TEST_02 or MY_FUNCTION

Three cases are possible :

A) The searched and replacement words have the same size :

For instance, if the searched word is device, whatever its capitalization form, and the exact replacement word is SySTeM, here are, below, the results of this S/R, for some forms of the searched word :

DeVIce => SySTem dEVicE => sYSteM devICe => sysTEm dEvIcE => sYsTeM B) The searched word have less letters than the replacement word :

For instance, if the searched word is device, whatever its capitalization form, and the exact replacement word is lOCatIOn, here are, below, the results of this S/R, for some forms of the searched word :

DeVIce => LoCAtiOn dEVicE => lOCatIOn devICe => locATiOn dEvIcE => lOcAtIOn

Note, in that example, that the 7th and 8th remaining letters, of the replacement word, which cannot be associated to a corresponding letter, in the searched word, keep their initial capitalization form !

C) The searched word have more letters than the replacement word :

For instance, if the searched word is device, whatever its capitalization form, and the exact replacement word is TeSt, here are, below, the results of this S/R, for some forms of the searched word :

DeVIce => TeST dEVicE => tESt devICe => tesT dEvIcE => tEsT

Remarks :

If a character of the searched word is NOT a letter, the associated character, in the replacement word, will NOT be changed

If a character of the replacement word is NOT a letter, it will NOT be changed, of course !

To perform these capitalization changes, TWO consecutive S/R will be mandatory.

In addition, I need a dummy character, NOT used yet, in your file. I chose the # character, but feel free to chose any other one !

So :

Let M be the number of letters of the SEARCHED word

Let N be the number of letters of the REPLACEMENT word

Then :

For case A) ( M = N ) OR case B) ( M < N )

FIRST S/R :

SEARCH (?i)\b<SEARCHED word, in ANY case>\b

REPLACE #<REPLACEMENT word, in ANY case>$0#

SECOND S/R :

SEARCH #|(?-is)(?=\w{<N>}(?:(\u)|(\l)))(\w)(?=\w*#)|(?i)<SEARCHED word, in ANY case>#

REPLACE \u(?1\3)\l(?2\3)

For case C) ( M > N )

FIRST S/R :

SEARCH (?i)\b(<The N FIRST letters>)(<The M-N LAST letters>)\b, of the SEARCHED word, in ANY case

REPLACE #<REPLACEMENT word, in ANY case>\1#\2

SECOND S/R :

SEARCH #|(?-is)(?=\w{<N>}(?:(\u)|(\l)))(\w)(?=\w*#)|(?i)<The N FIRST letters>#<The M-N LAST letters> , of the SEARCHED word, in ANY case

REPLACE \u(?1\3)\l(?2\3)

Then, from the examples, above :

For case A), from the original text :

DeVIce
dEVicE
devICe
dEvIcE

SEARCH (?i)\bdevice\b

REPLACE #system$0#

We obtain, after the 1ST S/R :

#systemDeVIce# #systemdEVicE# #systemdevICe# #systemdEvIcE#

SEARCH #|(?-is)(?=\w{6}(?:(\u)|(\l)))(\w)(?=\w*#)|(?i)device#

REPLACE \u(?1\3)\l(?2\3)

And, finally, after the 2ND S/R :

SySTem sYSteM sysTEm sYsTeM

For case B), from the original text :

DeVIce
dEVicE
devICe
dEvIcE

SEARCH (?i)\bdevice\b

REPLACE #location$0#

We obtain, after the 1ST S/R :

#locationDeVIce# #locationdEVicE# #locationdevICe# #locationdEvIcE#

SEARCH #|(?-is)(?=\w{8}(?:(\u)|(\l)))(\w)(?=\w*#)|(?i)device#

REPLACE \u(?1\3)\l(?2\3)

And, finally, after the 2ND S/R :

LoCAtion lOCatIon locATion lOcAtIon

For case C), from the original text :

DeVIce
dEVicE
devICe
dEvIcE

SEARCH (?i)\b(devi)(ce)\b

REPLACE #test\1#\2

We obtain, after the 1ST S/R :

#testDeVI#ce #testdEVi#cE #testdevI#Ce #testdEvI#cE

SEARCH #|(?-is)(?=\w{4}(?:(\u)|(\l)))(\w)(?=\w*#)|(?i)devi#ce

REPLACE \u(?1\3)\l(?2\3)

And, finally, after the 2ND S/R :

TeST tESt tesT tEsT

Best Regards,

guy038

P.S. : A last example, with my_function_n008 as a searched word and ABCD_123IjklmnOP as a replacement word, which, both, contain 16 characters !

So, Let’s supposed the example text, below :

My_Function_N008 mY_fUNCTION_n008 my_FUNCTION_n008 MY_fUnCtIoN_N008

SEARCH (?i)\bmy_function_n008\b

REPLACE #ABCD_123IjklmnOP$0#

We obtain, after this 1ST S/R :

#ABCD_123IjklmnOPMy_Function_N008# #ABCD_123IjklmnOPmY_fUNCTION_n008# #ABCD_123IjklmnOPmy_FUNCTION_n008# #ABCD_123IjklmnOPMY_fUnCtIoN_N008#

SEARCH #|(?-is)(?=\w{16}(?:(\u)|(\l)))(\w)(?=\w*#)|(?i)my_function_n008#

REPLACE \u(?1\3)\l(?2\3)

And, after the final 2ND S/R :

AbCD_123ijklMnOP aBCd_123IJKlmnOP abCD_123IJKlmnOP ABCd_123IjKlMnOP

Thanks guy038!

Looks good. Will be using this on Monday.

Best
Blair

@John-Ng

You could do “File” menu -> “Reload from Disk” – this will provide a point from which there is no further undo-ing.

@Kim-Kløve

You have the “Show End of Line” feature turned on. Turn off by the “View” menu, “Show Symbol” submenu. Uncheck “Show End of Line”.

Yes, we are running into this same issue as well.