Update of help for regexps required

[GoogleCodeExporter]

The screen with the regular expression search help (from the "replace" window) 
still lists '\(' and '\)' as "start of region" resp. "end of region" tokens.
However, these are simple parentheses '(' and ')' now, while searching for such 
parenthes requires a backslash as escape character.

From the announcement of version 4.2.25-rc1 (01.02.2011):
"The syntax for regular expression tagged regions has been simplified
from \(...\) to (...), called POSIX compatible mode in Scintilla. As a
consequence, bare ( and ) need to be matched using \( and \) in
regular expression mode."

I have not checked yet whether there are more such "hidden" changes from 4.1 to 
4.2, but maybe the help texts need to be adapted at other locations as well...

Original issue reported on code.google.com by goo...@robert-engelhardt.de on 25 May 2011 at 1:05

Attachments:

• RegExpHelp.png

[GoogleCodeExporter]

Well this is how it is in the official Notepad2. So send an email to Florian.

Original comment by XhmikosR on 25 May 2011 at 1:20

• Changed state: WontFix
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Uhm, sorry? Unless I'm completely blind, this lookup help is _NOT_ part of the 
official Notepad2. It's a (much welcome) improvement/addition of the mod 
version...

Original comment by goo...@robert-engelhardt.de on 25 May 2011 at 2:48

[GoogleCodeExporter]

True, I missed that. Anyway, I don't use this feature so I don't know what 
works and what not. Give me this info and I'll change the help window text.

Original comment by XhmikosR on 25 May 2011 at 2:56

• Changed state: New

[GoogleCodeExporter]

fixed in r509

Original comment by XhmikosR on 25 May 2011 at 3:29

• Changed state: Fixed

[GoogleCodeExporter]

Thanks, that was quick! Now having reviewed the notepad helpfile, I would 
recommend to add the following syntax descriptions as well, at the appropriate 
locations:

"?           Matches preceding 0 or 1 times" (suggestion: before '*' and '+' 
rows)
"*? or +?    Non greedy matching of quantifiers '?' and '+'" (directly after 
'*' and '+' rows)
"\x          Escape character with otherwise special meaning" (maybe near the 
beginning?)

(or similar texts, whatever fits into the window). This way the overview more 
or less matches the syntax described in the helpfile again...

Oh, and for the window with the backslash transformations, the hex code syntax 
"\u####" should be added (another new feature of version 4.2.25).

Thanks for caring also about the fine details!

Original comment by goo...@robert-engelhardt.de on 25 May 2011 at 11:40

[GoogleCodeExporter]

I'm not sure if I really want to all these. I'll decide later.

Original comment by XhmikosR on 26 May 2011 at 10:49

• Changed state: New

[GoogleCodeExporter]

Original comment by XhmikosR on 26 May 2011 at 10:35

• Changed state: Fixed