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

[regex-coach] An error of type #:|<Dummy Symbol Name>| occured
by Darke, Clive 09 May '11

09 May '11

I'm using Regex Coach Version 0.9.2 on Windows 7 Professional (SP 1). I installed and ran it OK, until I loaded a Microsoft Office Word document into it to test \x matching. I closed down Regex Coach with that document loaded. Now, when I run the program I always get a Message Box with: "An error of type #:|<Dummy Symbol Name>| occured, arguments : (:SIZE 151983)" I uninstalled Regex Coach, rebooted, then installed it again, but it still gives this error. I have RegEx Coach installed on the same version of Windows 7 on another machine and I have no problems - but I have not tried loading a Word doc into it! >From the doc: "The contents of these two panes will also remain persistent between two invocations of The Regex Coach. " My best guess it that the uninstall is not destroying the persistent data, even between reinstalls, but I can't figure out where it is being stored. Any ideas? Clive Darke ________________________________ QA works with organisations to transform performance through learning. We are dedicated to making our clients more successful through the provision of world-class training services. To find out more visit www.qa.com The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. QA Ltd. Rath House, 55-65 Uxbridge Road, Slough, Berkshire,SL1 1SG. QA Ltd. is a company registered in England with company registration number:2413137 Scanned by ICRITICAL

1 0

[regex-coach] a possible bug in regular expression word boundaries handling
by Sten Wolf 16 Nov '10

16 Nov '10

trying out regex coach I discovered something that might be a bug - the handling of word boundaries \< and \> specifically - trying to match the first word in each line in a multiple line target string: ^\<.*\> treats \< and \> as the characters < and > respectively.

2 1

[regex-coach] feature request - more than 10 highlight buttons for captured groups
by Noel Golding 23 Jun '10

23 Jun '10

Is it possible to allow for more than 10 highlight buttons for captured groups? -Noel

2 2

[regex-coach] alternations working differently in Regex Coach versus perl program.
by Troy Peterson 19 Sep '09

19 Sep '09

I am writing a regex to test for valid dates in YYYY-MM-DD format. Using this regex in a perl test program I get positive results for all dates for the next 365 days. Regex Coach however failes to match some such as '2010-06-30'. I assume this is because of the order of the alternations and the regex wanting to match a sub-pattern as quickly as possible. I can resolve the issue in The Regex Coach by adding () around the month and year patterns. I would like to know why there is a difference between my Perl program and Regex Coach. Could this be implementation dependent. Both my program and its output are below. I tend to think that The Regex Coach got this right. (?# regex in The Regex Coach) * [123456789]\d\d\d- # year * * (?: * * (?:0[13578]|10|12 - [012][123456789]|10|20|30|31) | # Months with 31 days* * (?:0[469]|11 - [012][123456789]|10|20|30 ) | # Months with 30 days * * (?:02 - [012][12345678]||10|20|19 ) # Febuary* * )* ### perl Test program #!/iw-home/teamsite/iw-perl/bin/iwperl use strict; use warnings; use Carp; use Getopt::Long; use Pod::Usage; use Cwd; use Date::Calc qw(:all); my $dateregex = qr{ [123456789]\d\d\d- # year (?: (?:0[13578]|10|12 - [012][123456789]|10|20|30|31) | # Months with 31 days (?:0[469]|11 - [012][123456789]|10|20|30 ) | # Months with 30 days (?:02 - [012][12345678]||10|20|19 ) # Febuary ) }smx; sub testdate { my ($d) = (@_); print "$d"; if ( $d =~ m{$dateregex}smx ) { print "okay\n"; } else { print "\n"; croak "broken"; } } foreach my $d ( 1 .. 365 ) { my ( $year, $month, $day, $hour, $min, $sec, $doy, $dow, $dst ) = System_Clock(); ( $year, $month, $day, $hour, $min, $sec ) = Add_Delta_DHMS( $year, $month, $day, '0', '0', '0', "$d", '0', '0', '0' ); my $td = sprintf( "%4d-%02d-%02d", $year, $month, $day ); testdate("$td"); } exit; ##OUTPUT 2009-08-03okay 2009-08-04okay 2009-08-05okay 2009-08-06okay 2009-08-07okay 2009-08-08okay 2009-08-09okay 2009-08-10okay 2009-08-11okay 2009-08-12okay 2009-08-13okay 2009-08-14okay 2009-08-15okay 2009-08-16okay 2009-08-17okay 2009-08-18okay 2009-08-19okay 2009-08-20okay 2009-08-21okay 2009-08-22okay 2009-08-23okay 2009-08-24okay 2009-08-25okay 2009-08-26okay 2009-08-27okay 2009-08-28okay 2009-08-29okay 2009-08-30okay 2009-08-31okay 2009-09-01okay 2009-09-02okay 2009-09-03okay 2009-09-04okay 2009-09-05okay 2009-09-06okay 2009-09-07okay 2009-09-08okay 2009-09-09okay 2009-09-10okay 2009-09-11okay 2009-09-12okay 2009-09-13okay 2009-09-14okay 2009-09-15okay 2009-09-16okay 2009-09-17okay 2009-09-18okay 2009-09-19okay 2009-09-20okay 2009-09-21okay 2009-09-22okay 2009-09-23okay 2009-09-24okay 2009-09-25okay 2009-09-26okay 2009-09-27okay 2009-09-28okay 2009-09-29okay 2009-09-30okay 2009-10-01okay 2009-10-02okay 2009-10-03okay 2009-10-04okay 2009-10-05okay 2009-10-06okay 2009-10-07okay 2009-10-08okay 2009-10-09okay 2009-10-10okay 2009-10-11okay 2009-10-12okay 2009-10-13okay 2009-10-14okay 2009-10-15okay 2009-10-16okay 2009-10-17okay 2009-10-18okay 2009-10-19okay 2009-10-20okay 2009-10-21okay 2009-10-22okay 2009-10-23okay 2009-10-24okay 2009-10-25okay 2009-10-26okay 2009-10-27okay 2009-10-28okay 2009-10-29okay 2009-10-30okay 2009-10-31okay 2009-11-01okay 2009-11-02okay 2009-11-03okay 2009-11-04okay 2009-11-05okay 2009-11-06okay 2009-11-07okay 2009-11-08okay 2009-11-09okay 2009-11-10okay 2009-11-11okay 2009-11-12okay 2009-11-13okay 2009-11-14okay 2009-11-15okay 2009-11-16okay 2009-11-17okay 2009-11-18okay 2009-11-19okay 2009-11-20okay 2009-11-21okay 2009-11-22okay 2009-11-23okay 2009-11-24okay 2009-11-25okay 2009-11-26okay 2009-11-27okay 2009-11-28okay 2009-11-29okay 2009-11-30okay 2009-12-01okay 2009-12-02okay 2009-12-03okay 2009-12-04okay 2009-12-05okay 2009-12-06okay 2009-12-07okay 2009-12-08okay 2009-12-09okay 2009-12-10okay 2009-12-11okay 2009-12-12okay 2009-12-13okay 2009-12-14okay 2009-12-15okay 2009-12-16okay 2009-12-17okay 2009-12-18okay 2009-12-19okay 2009-12-20okay 2009-12-21okay 2009-12-22okay 2009-12-23okay 2009-12-24okay 2009-12-25okay 2009-12-26okay 2009-12-27okay 2009-12-28okay 2009-12-29okay 2009-12-30okay 2009-12-31okay 2010-01-01okay 2010-01-02okay 2010-01-03okay 2010-01-04okay 2010-01-05okay 2010-01-06okay 2010-01-07okay 2010-01-08okay 2010-01-09okay 2010-01-10okay 2010-01-11okay 2010-01-12okay 2010-01-13okay 2010-01-14okay 2010-01-15okay 2010-01-16okay 2010-01-17okay 2010-01-18okay 2010-01-19okay 2010-01-20okay 2010-01-21okay 2010-01-22okay 2010-01-23okay 2010-01-24okay 2010-01-25okay 2010-01-26okay 2010-01-27okay 2010-01-28okay 2010-01-29okay 2010-01-30okay 2010-01-31okay 2010-02-01okay 2010-02-02okay 2010-02-03okay 2010-02-04okay 2010-02-05okay 2010-02-06okay 2010-02-07okay 2010-02-08okay 2010-02-09okay 2010-02-10okay 2010-02-11okay 2010-02-12okay 2010-02-13okay 2010-02-14okay 2010-02-15okay 2010-02-16okay 2010-02-17okay 2010-02-18okay 2010-02-19okay 2010-02-20okay 2010-02-21okay 2010-02-22okay 2010-02-23okay 2010-02-24okay 2010-02-25okay 2010-02-26okay 2010-02-27okay 2010-02-28okay 2010-03-01okay 2010-03-02okay 2010-03-03okay 2010-03-04okay 2010-03-05okay 2010-03-06okay 2010-03-07okay 2010-03-08okay 2010-03-09okay 2010-03-10okay 2010-03-11okay 2010-03-12okay 2010-03-13okay 2010-03-14okay 2010-03-15okay 2010-03-16okay 2010-03-17okay 2010-03-18okay 2010-03-19okay 2010-03-20okay 2010-03-21okay 2010-03-22okay 2010-03-23okay 2010-03-24okay 2010-03-25okay 2010-03-26okay 2010-03-27okay 2010-03-28okay 2010-03-29okay 2010-03-30okay 2010-03-31okay 2010-04-01okay 2010-04-02okay 2010-04-03okay 2010-04-04okay 2010-04-05okay 2010-04-06okay 2010-04-07okay 2010-04-08okay 2010-04-09okay 2010-04-10okay 2010-04-11okay 2010-04-12okay 2010-04-13okay 2010-04-14okay 2010-04-15okay 2010-04-16okay 2010-04-17okay 2010-04-18okay 2010-04-19okay 2010-04-20okay 2010-04-21okay 2010-04-22okay 2010-04-23okay 2010-04-24okay 2010-04-25okay 2010-04-26okay 2010-04-27okay 2010-04-28okay 2010-04-29okay 2010-04-30okay 2010-05-01okay 2010-05-02okay 2010-05-03okay 2010-05-04okay 2010-05-05okay 2010-05-06okay 2010-05-07okay 2010-05-08okay 2010-05-09okay 2010-05-10okay 2010-05-11okay 2010-05-12okay 2010-05-13okay 2010-05-14okay 2010-05-15okay 2010-05-16okay 2010-05-17okay 2010-05-18okay 2010-05-19okay 2010-05-20okay 2010-05-21okay 2010-05-22okay 2010-05-23okay 2010-05-24okay 2010-05-25okay 2010-05-26okay 2010-05-27okay 2010-05-28okay 2010-05-29okay 2010-05-30okay 2010-05-31okay 2010-06-01okay 2010-06-02okay 2010-06-03okay 2010-06-04okay 2010-06-05okay 2010-06-06okay 2010-06-07okay 2010-06-08okay 2010-06-09okay 2010-06-10okay 2010-06-11okay 2010-06-12okay 2010-06-13okay 2010-06-14okay 2010-06-15okay 2010-06-16okay 2010-06-17okay 2010-06-18okay 2010-06-19okay 2010-06-20okay 2010-06-21okay 2010-06-22okay 2010-06-23okay 2010-06-24okay 2010-06-25okay 2010-06-26okay 2010-06-27okay 2010-06-28okay 2010-06-29okay 2010-06-30okay 2010-07-01okay 2010-07-02okay 2010-07-03okay 2010-07-04okay 2010-07-05okay 2010-07-06okay 2010-07-07okay 2010-07-08okay 2010-07-09okay 2010-07-10okay 2010-07-11okay 2010-07-12okay 2010-07-13okay 2010-07-14okay 2010-07-15okay 2010-07-16okay 2010-07-17okay 2010-07-18okay 2010-07-19okay 2010-07-20okay 2010-07-21okay 2010-07-22okay 2010-07-23okay 2010-07-24okay 2010-07-25okay 2010-07-26okay 2010-07-27okay 2010-07-28okay 2010-07-29okay 2010-07-30okay 2010-07-31okay 2010-08-01okay 2010-08-02okay

3 2

Re: [regex-coach] Regex Coach/CL-PPCRE question
by Edi Weitz 25 Jun '09

25 Jun '09

[Cc to mailing list.] Thanks for the report, this definitely looks like a bug. I'll see to have this fixed in the next release. Cheers, Edi. On Wed, Jun 24, 2009 at 10:45 PM, Dan Moniz<dnm(a)pobox.com> wrote: > Hi there, > > I'm using Regex Coach 0.9.2 (built with CL-PPCRE 1.3.2) and noticed > some unexpected behavior when using the \b token. It seems to be > working fine, but the Info tab displays "the selection is NIL" for the > token, rather than the expected word boundary explanation. It *does* > seem to get \B (the negation of \b) right: "the selection is a space > between two characters which is not a word boundary". > > I initially discovered this while trying to troubleshoot and test a > regex from another system/product (unrelated, and at present I'm not > certain what regex engine it uses, though I'm assuming PCRE or POSIX > with GNU extensions): > > regex: type\b\w*?\btext\b\w*?\bjavascript > > using Regex Coach's Info and Tree tabs to "debug" the expression and > why it wasn't seeming to match a string I though it should. Initially > I thought \b might be unsupported, but it does seem to work in a > simpler test case: > > regex: \bis\b > string: This island is beautiful > > The CL-PPCRE documentation confirmed that both \b and \B were > supported as well. Nonetheless, the NIL replacement in the Info tab > was odd. > > FWIW, I'm running on Windows Vista Ultimate with SP1 installed. > > Hope this helps. Thanks for making Regex Coach, and thanks for making > it available. > > > -- > Dan Moniz <dnm(a)pobox.com> [http://pobox.com/~dnm/] > >

1 0

[regex-coach] Please implement variable length look-behind functionality
by Alex Grässer 25 Jun '09

25 Jun '09

Hi Edmund Thank you very much for Regex Coach. It has helped tremendously! Recently I needed to use a negative look-behind with multiple exclusions and found that Regex Coach does not support variable length look-behind. \\[^\\]*(?<!(tmp|files))$ gives an error that "Variable length look-behind not implemented (yet)" whereas \\[^\\]*(?<!(tmp|les))$ works, except that it excludes more than required. Interestingly WinMerge also has this restriction ;-) Thanks Alex

2 3

[regex-coach] The Regex Coach 0.9.2 works on Linux under Wine
by JP Vossen 22 Mar '09

22 Mar '09

FYI, The Regex Coach 0.9.2 (and 0.9.1) works just fine on my Ubuntu 8.04 and 8.10 Linux under Wine (Wine Is Not an Emulator). HOWTO: Type (or copy & paste) these commands in a terminal window. Note the '$' represents the (non-root) user prompt. $ sudo aptitude install wine wget $ wget 'http://www.kegel.com/wine/winetricks' $ bash ./winetricks vcrun2005sp1 vcrun2008 $ wget -O regex-coach-0.9.2.exe 'http://weitz.de/files/regex-coach.exe' $ wine ./regex-coach-0.9.2.exe Notes: * regex-coach-0.9.2.exe is just the usual TRC installer * You will find the tool in the Applications, Wine, Programs, The Regex Coach menu. * Do NOT install Wine directly from the web, use the package management system (usually RPM or APT/deb) built-in to your Linux distro and version. If you stray from that you will regret it sooner or later--probably sooner. Trust me. References: http://en.wikipedia.org/wiki/Wine_(software) http://www.winehq.org/ http://wiki.winehq.org/winetricks Hope this is useful, JP PS--It might be useful to update the "Older versions, Linux, FreeBSD, Mac" section of http://www.weitz.de/regex-coach/, since it is so easy to get it working. ----------------------------|:::======|------------------

1 0

[regex-coach] Feature req: possessive quantifier support (revisited)
by Ben Golding 16 Feb '09

16 Feb '09

Hi all, I already checked the archives for this issue and it seems I am not the first to ask: http://common-lisp.net/pipermail/regex-coach/2005-April/000282.html The response from Edi at that time: "Standalone" regular expressions ("atomic grouping") as in (?>x+) are supported, possesive quantifiers as in x++ aren't because they aren't in Perl and CL-PPCRE tries to be compatible with Perl. That was in 2005. Indeed, using an older Perl: % perl -e "print 'no' if '123456' !~ /\d++6/" Nested quantifiers in regex; marked by <-- HERE in m/\d++ <-- HERE 6/ at -e line 1. % perl -v This is perl, v5.8.3 built for sun4-solaris ... However, now Perl has changed: >perl -le "print 'no' if '123456' !~ /\d++6/" no >perl -v This is perl, v5.10.0 built for MSWin32-x86-multi-thread ... Could be a limitation of CL-PPCRE or could be that the Regex Coach only needs updated, I'm not sure on this. Regards Ben Golding

2 1

[regex-coach] Couple more minor feature suggestions
by DJ 28 Jan '09

28 Jan '09

Hi Regex-coach, A couple more "minor" feature suggestions. 1) Step Tab Add a "Previous step" button. 2) Step Tab Add logging. Perhaps a "Log" pane that could be saved, or at least cut/paste. 3) Help | Documentation When I clicked Help | Documentation nothing occurred. I thought it might just take the user to the web Quick Start Tutorial. 4) Step Tab At some point I must have selected the regular expression in the Step tab Regular expression pane at the bottom. When selected the background is grey. When I then clicked on the "Next Step" button, the helpful red background coloring wasn't appearing in the Step tab Regular expression pane to indicate the regex position. The same thing happens if the user (me :-)) selects the text in the Step tab Target string pane. The yellow/grey coloring doesn't appear. I might have used the mouse as I was thinking about things, and that is when the selection occurred. I couldn't figure out why the red/yellow/grey highlighting wasn't working :-) when I was clicking the Start and Next buttons. Maybe when the user clicks on the "Start" button remove all the selections (i.e., the text background is white) in both Step panes. Environment: Win/XP and Regex Coach 0.9.2 Thank you. -- __________________________ DJ

2 1

[regex-coach] Couple minor feature suggestions
by DJ 28 Jan '09

28 Jan '09

Hi Regex-coach, The example on, "http://www.weitz.de/regex-coach/tutorial18.html", and the Regex Coach Step feature have been helpful, especially in understanding backtracking. I have a couple minor feature suggestions. 1) Step Tab Keep track of and display the number of times the "Next Step" button is clicked, and append it to the message, like: 19) Sub-match from 2 to 3 2) Info Tab At first glance I thought regex-coach Info pane didn't explain lookahead/lookbehind because of the message, "The selection is invalid", but then I extended the selection. The regular expression I used was, "(?<=\d)(?=(\d\d\d)+(?!\d))". Perhaps the text could provide a suggestion, like: "Did you mean "(?<=\d)"", when a user selects an incomplete expression like "?<=". When I selected "?:" or "(?:[a]*b|a+ac)", in "(?:[a]*b|a+ac)y", no additional information was provided in the Info Pane for the Group No Capture. Although the Control Tab does represent that, it would be nice if it were reflected in the Info pane too. 3) File menu Add a Clear menu item that would clear the current contents of the Regular expression pane and the Target string pane. If not Clear, maybe Reset or New. File | Clear (Alt+C) maybe? Or File | Clear | Both (Alt+C) File | Clear | Regular expression pane File | Clear | Target string pane 4) File menu Rather than relying on which pane has the focus, add a specific submenu to "File | Insert File" to position the text, like: File | Insert File | Regular expression pane File | Insert File | Target string pane Maybe extend this to Save too. File | Save | Both File | Save | Regular expression pane File | Save | Target string pane Very nice. I haven't touched LISP since my college days (I still have my "Learning LISP" handbook :-) and it was fun to see it used. Thank you. -- __________________________ DJ

2 1