- regex-coach@common-lisp.net - mailman3.common-lisp.net

[regex-coach] feature request: Named Groups
by Randy Gerritse 30 Aug '05

30 Aug '05

Hi First of all I've gotta say, having tested all the available regex tools, your regex coach is farout the best. However, one thing has been bugging me A LOT. You don't seem to support named groups! Since this makes the output in the language I use, PHP, a lot more userfriendly (and less subject to change if you alter the expression) I use this language feature a lot: class="cell2">.*?(?P<downloads>(\d{1,3},{0,1}){0,5})\s*& .*?class="cell5">(?P<requirements>.*?)<\/td> .*?<td>Publisher:<\/td> \s*<td>(?P<publisher>.*?)<\/td> .*?<td>Limitations:<\/td> \s*<td>(?P<limitations>.*?)<\/td> .*?<td>Date.added:<\/td> \s*<td>(?P<published>.*?)<\/td> .*?<div.id="desc-body">\s*?(?P<longdesc>.*?)\s*?<\/div> like in the above example (which by the way your tool processes correctly except for the named groups, where most other tested tools failed!) in the documentation I found it says that this format: (?P<longdesc>group) ...has been adapted from python and made part of the standard... is there a reason you have not put it in the tool? and is it possible to start supporting it? that would be a BIG help!!! right now I need to strip out all names before testing and that sux0rs... it would make your tool the best out there, by a mile..!

2 1

[regex-coach] Apparent crash on complex regex in "Tree" tab
by era+regex=coach＠iki.fi 30 Aug '05

30 Aug '05

I came across your tool, and while it appears interesting, the first thing I tried it with appears to have crashed it somehow. I was trying to run a SpamAssassin rule against a message from the SpamAssassin public corpus. Both of these are publicly available from http://www.spamassassin.org but for completeness, I am also attaching them below in exactly the form I was using them. Running the regex from 20_head_tests_cf_UNRESOLVED_TEMPLATE.txt with the /m modifier against the message headers in easy_ham_00001-head.txt and clicking on the "Tree" tab causes a lot of output to be printed on standard output (cf. third attachment) and the main window to disappear after a short while. The process is still alive, consuming around 90-95% of the CPU, though not producing a lot of load (load average still well below one). I finally killed it after allowing it to run for some 10 minutes wall clock time. Incidentally, ctrl-C causes a message "Quittingregex-coach/regex-coach : Interrupted - quitting" to be printed (on standard output, not standard error, sigh), but does not kill the process. PS. Would you mind if your list was signed up for Gmane <http://www.gmane.org/>? If I go ahead and sign up the list, do you have an mbox archive handy which could be imported into Gmane? /* era */ -- If this were a real .signature, it would suck less. Well, maybe not.

2 1

[regex-coach] Re: ^123$, Str:123; Result:No match ???
by Edi Weitz 06 Aug '05

06 Aug '05

[Please send questions and bug reports to the mailing list. The address is /not/ regex-coach-owner(a)common-lisp.net but regex-coach(a)common-lisp.net. You have to subscribe first.] On Sat, 6 Aug 2005 16:23:24 +0530, "Nithyanandham, M" <Nithyanandham.M(a)siemens.com> wrote: > I currently use regex-coach that is developed by you. It is really > helpful to learn regular expression very fast. Meanwhile, I just > found one bug with it and hence I wanted to inform you. > > Regular expression: > ^123$ > > Target string: > 123 > > Result: No match. > > Isn't that incorrect result? That would be incorrect. I can't reproduce that, though. If I enter these strings The Regex Coach shows a match. Are you using the newest version (0.6.7)? Maybe there's some whitespace or some hidden character in either the regex or the target string? Cheers, Edi.

1 0

[regex-coach] (no subject)
by Chris Wood 15 Jun '05

15 Jun '05

Is The Regex Coach compatable with preg AND ereg, ie, Perl and POSIX style? - Chris Wood Wellington, New Zealand

2 1

[regex-coach] Feature request: Regexp performance indicator/steps used
by Morten Hattesen 03 May '05

03 May '05

I really appreciate what Regex Coach has done for honing my Regular Expressions skills, and assisting debugging of complex expressions. I frequently wish to optimize regular expressions (mainly by reducing possible backtracking http://www.regular-expressions.info/atomic.html) but lack a way to test the relative performance between different regular expressions. To measure performance of a given regexp, I would really like the possibility of having Regex Coach count the total number of steps used by the underlying regexp engine for a given regexp search, or some other meaningful performance indicator. This could possibly be displayed when pressing the ">>" (show next match) button (regardless of whether a match was found or not). This way, you can quickly try out different matching approaches, and get an indication of the relative performance. Rgds, Morten Hattesen

2 2

[regex-coach] possessive quantifiers not supported?
by Thomas Ilsche 03 Apr '05

03 Apr '05

Hi, i'm new here and I relaly like regex-coach. I use it to develop regexps that i use with php/pcre. However when it comes to regexp containing possessive quantifiers they seem not to be supported. I am wondering if this is a problem with the CL-PPCRE or regex-coach? -- Best regards, Thomas mailto:ThomasIlsche@gmx.de

2 1

[regex-coach] Re: perl regex
by Edi Weitz 18 Mar '05

18 Mar '05

Please send questions to the mailing list. On Fri, 18 Mar 2005 19:42:53 -0000, "Henry O'Keeffe" <hok2005(a)lazydba.com> wrote: > test.pl > > #!/home/perl/bin/perl > > $string="im not seeing any yellow"; > if ($string =~ /l*/) > { > print "Should be seeing yellow\n"; > } > else > { > print "Shouldn't be seeing yellow\n"; > } > > > > $ perl test.pl > > Should be seeing yellow Look closely at the screenshot you sent and you'll see the line "Match from 0 to 0" Then try this: edi@miles:/tmp$ perl -le 'print "Match" if "xxx" =~ /l*/' Match edi@miles:/tmp$ perl -le 'print "Match: #$1#" if "xxx" =~ /(l*)/' Match: ##

1 0

RE: [regex-coach] CAPI
by Allen, Greg 04 Mar '05

04 Mar '05

It would be great if one day some rather adventurous soul, say, ported the CL-PPCRE code to run under a JVM hosted common lisp (e.g. http://www.cliki.net/Armed%20Bear%20Lisp) and ported the GUI to IBM's attractive SWT gui... Of course that adventurous soul might want to get their fingers on your CAPI based GUI, and you may have reasons for not distributing it? wishful thinking. Greg PS. thanks for regex-coach! -----Original Message----- From: regex-coach-bounces(a)common-lisp.net [mailto:regex-coach-bounces@common-lisp.net] On Behalf Of Edi Weitz Sent: Thursday, March 03, 2005 5:36 PM To: Andreas Davour Cc: regex-coach(a)common-lisp.net Subject: Re: [regex-coach] Strange fatal error On Thu, 3 Mar 2005 09:45:48 +0100 (CET), Andreas Davour <ante(a)Update.UU.SE> wrote: > You wouldn't mind expanding a bit upon that position? Sure. What do you want to know? > I could probably have solved this problme myself in 10 minutes if I > had the source Probably not. The way OpenMotif is found is hard-coded into CAPI and can't be changed even if you have the source code to Regex Coach. > and contributed code to make your program even better. So, you're an experienced Common Lisp hacker? > And, you mean, it's not possible to build without one? Why? Because it relies on CAPI for the GUI part. Without the GUI it's not much more than my CL-PPCRE library which is already available in source form. There are several free Common Lisp compilers available for FreeBSD so you can hack it as much as you like. Cheers, Edi. _______________________________________________ regex-coach site list regex-coach(a)common-lisp.net http://common-lisp.net/mailman/listinfo/regex-coach ------------------------------------------------------------------------------ This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.

2 1

[regex-coach] Strange fatal error
by Andreas Davour 03 Mar '05

03 Mar '05

When I tried to run regexp-coach under FreeBSD (with Linux compatibility enabled) I happened upon the following strange error: Error: Could not register handle for external module #:CAP: libXm.so.3: cannot open shared object file: No such file or directory. 20957C18 20207EDC -> 20207E02 = #:DEB 20957C34 20055887 -> 20055812 = (#:SYM 2176) 20957C5C 2020823F -> 202080EA = #:CON 20957C88 20167D82 -> 20167CB2 = (#:SYM 1636) 20957C9C 20167FD8 -> 20167F6A = (#:SYM 5419) 20957CC4 2017213B -> 2017205A = (#:SYM 694) 20957D04 2021438D -> 20214372 = (#:SYM 5567) 20957D10 20485A00 -> 204859A2 = (#:SYM 5374) 20957D18 205B6440 -> 205B6422 = #<function 205B6422> 20957D28 204A38B7 -> 204A37A2 = #<function 204A37A2> 20957E00 20186E0B -> 20186DE2 = (#:SYM 4003) 20957E10 20186EFA -> 20186E92 = (#:SYM 4732) Then I did: ante@Upheaval$ locate libXm.so.3 /usr/X11R6/lib/libXm.so.3 ante@Upheaval$ So, after trussing the image I realize that it's doing some very odd stuff. How about distributing this as source instead? Or can someone produce a FreeBSD version of this program for me? /Andreas -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?

2 5

[regex-coach] Re: Your Regular Expressions software
by Edi Weitz 28 Dec '04

28 Dec '04

Hi! On Mon, 27 Dec 2004 00:40:54 -0500, "Jeff ADA" <jeff12(a)fastpitchcentral.com> wrote: > I just downloaded your "regular expressions" software. I love the > concept! Please notify me after you've made your next major update. New releases will be announced on the mailing list (see Cc) which should also be used for bug reports and suggestions. <http://weitz.de/regex-coach/#mail> > 1. I'm using PHP and they have a separate function for multiple > matches of the same pattern. Something like that would be useful as > an option. Well, you already have multiple matches, kind of - see the scan buttons, the split pane and the 'g' modifier. > 2. When multiple matches occur it would be useful to highlight each > match in a different color. With one pattern that matches 6 times > the first five were in yellow and the last one was in orange. I had > specified {2,6}. This is something that others have also suggested and it's likely to be in one of the next releases. > 3. The relative sizes of the four text-areas used should be able to > be dynamically changed by moving their top or bottom lines up or > down. For example, I wanted to see multiple lines of the match > process when I only had a single line of pattern. And, I didn't > really need to see the text being matched (2nd area) since that's > what I was following in the 4th area. All text panes can be resized: <http://weitz.de/regex-coach/#resize> > This and the next point combined are probably why I wouldn't use > your wonderful tool every day - and be happy to pay you for it! I don't think enough people would pay for this application to warrant investing more time in it. I had more than 100,000 downloads so far and seven (7) of those who downloaded made a donation to PayPal. Go figure... :) > 4. There needs to be something other than just a checkbox for > verbose. Something like #operations, #characters, #lines or > something that lets me skip a bunch of checks until I get to the > point of wanting to see a certain part of the input being matched by > the pattern. I had to click more than 400 times and then I > discovered my pattern was working all along and the input text I > gave you was not the same input as I was using. I'll keep that suggestion in mind but the stepper (and the whole matching process) is a little bit more complicated and doesn't lend itself very well to simple linear counting like "number of characters" or such. Thanks for your feedback. Happy New Year, Edi.

1 0