Page 1 of 1

Saved regular expressions.

Posted: Mon Aug 09, 2004 7:52 pm
by farmersckn
It would be nice if there was a little "..." button next to the regular expression search field (and replacement field too!) that brought up a list of all teh regular expressions you have used.
It would be able to connect search expressions with replacement expressions, keeping them linked...
It would allow you to name a search/replace pair (to explain what the regexp does!)
It would allow you to delete certain regexp pairs if you don't want them anymore.
It wouldn't have a limit on the number that can be stored.
It would preferably save your preference as to whether it should be run throughout the file or only the selection, preserve case, etcetera....
Also what might be a nice addition is a Regexp builder! It wouldn't be too hard to implement ( I don't think). Just have some buttons for ALPHA, UPPER, then MORE THAN ONE, ONE only, ZERO or MOre, etcetera... I might write a regexp builder actually...

The reason I make this request is because I use the same regular expressions quite often. They can be long and tedious so its not practical to type them in each time. I search so much that the little dropdown menu runs out of space for my regexps sometimes. So i have to cut/paste from a notepad file in the meantime. Hopefully some others will see some usefulness in this idea and give it support!

Posted: Mon Aug 09, 2004 9:14 pm
by s_reynisson
I've already got something in TP that does most of the things you talk about, it's called a "book", see TP's help file under errr... "Clip library".
But that involves some pasting so I'd vote for your method any day!

Posted: Tue Aug 10, 2004 4:51 pm
by farmersckn
So i created my own clip library with some handy regexp shortcuts so i don't have to remember what I need to type to get it to recognize an identifier/token which symbol is one or more, only one or zero, or zero or more and its a handy addition... but it still like you said requires tedious cut/pasting. Hopefully a save feature will be implemented. Thanks for the workaround in the meantime!