regx backslashed parens make me miserable

[roadworrier]

I guess the subject line says it all, but I'd really much rather backslash parens when I rarely use them, than have to backslash the parens every time I'm trying to get replace values. I've been using TextPad for years (and I love TextPad), but it finally just bugged me enough to post this comment.
This was the search and replace I just did:
"\([^"]*\)"\([^"]*\)"\([^"]*\)",
"\3"\2"\1",

(in addition to being less annoying, getting rid of the parents would match perl s// and other unix search and replaces like that...)

[BenjiSmith]

Amen to that. The backslashed parentheses drive me fucking insane.

[s_reynisson]

Hmm, while I make no claims to be counted as sane, I do use POSIX style regex's (which can be selected from the Editor page of the Preferences dialog box). The diffrence you can see in TP's help file under "How to Use Regular Expressions", a table that lists the Default Operator and the POSIX Operator. HTH

[Bob Hansen]

Enhancements not need to correct that backslash issue with RegEx.

The default is not to use POSIX syntax.

Easy to correct:
Configure, Preferences, Editor.
Put a checkmark in "Use POSIX regular expression syntax"
Apply and Save the change.

[roadworrier]

cool! thank you guys for letting me know all I needed to do was go POSIX!!! I'm sooo much happier now!