From edi at agharta.de Fri Apr 7 20:36:14 2006 From: edi at agharta.de (Edi Weitz) Date: Fri, 07 Apr 2006 22:36:14 +0200 Subject: [regex-coach] New release 0.8.4 Message-ID: ChangeLog: Version 0.8.4 2006-04-07 Fixed bug in output when a tilde appeared in regular expression (caught by anton m) Added info about FreeBSD (thanks to Jim Prewett) Download: http://weitz.de/files/regex-coach.exe http://weitz.de/files/regex-coach.tgz Cheers, Edi. From edi at agharta.de Sat Apr 15 19:12:14 2006 From: edi at agharta.de (Edi Weitz) Date: Sat, 15 Apr 2006 21:12:14 +0200 Subject: [regex-coach] Re: Regex-coach In-Reply-To: <1145112701.6489.2.camel@ws.unikorn.afraid.org> =?iso-8859-1?q?=28=DE=F3r=F0ur_J=F3nsteinsson's?= message of "Sat, 15 Apr 2006 14:51:40 +0000") References: <1145112701.6489.2.camel@ws.unikorn.afraid.org> Message-ID: [Please use the mailing list for bug reports.] On Sat, 15 Apr 2006 14:51:40 +0000, ??r?ur J?nsteinsson wrote: > I am, or ... was, a happy user of the regex-coach, under linux. I am > having problems starting it up after I upgraded my desktop computer > from Fedora Core 4 to Fedora Core 5, when starting from a Terminal I > get the following... > > ------------------------------ > [unikorn at ws regex-coach]$ ./regex-coach > Warning: Unknown map line : [ 00718000-00719000 r-xp 00718000 00:00 0 > [vdso] ] > Warning: Unknown map line : [ 091c8000-091f9000 rwxp 091c8000 00:00 0 > [heap] ] > Error: Could not register handle for external module #:CAP: > libXm.so.2: cannot open shared object file: No such file or directory. > 208FC138 201E4424 -> 201E434A = #:DEB > 208FC154 2029F647 -> 2029F5D2 = (#:SYM 5800) > 208FC17C 201E48FC -> 201E4792 = #:CON > 208FC1A8 2068F444 -> 2068F372 = (#:SYM 547) > 208FC1BC 2068F0D8 -> 2068F06A = (#:SYM 1763) > 208FC1E4 201E058B -> 201E04AA = (#:SYM 1674) > 208FC224 2079D755 -> 2079D73A = (#:SYM 3479) > 208FC230 2079D920 -> 2079D8C2 = (#:SYM 4000) > 208FC238 2035EFC0 -> 2035EFA2 = 0 > 208FC248 2028BF37 -> 2028BE22 = 0 > 208FC320 201B40DB -> 201B40B2 = (#:SYM 5276) > 208FC330 201BD8B2 -> 201BD84A = (#:SYM 4734) > [unikorn at ws regex-coach]$ > ------------------------------ > > I hope you could fix this for the next version You're missing OpenMotif/Lesstif or you have a wrong version of it installed. Search the archives of the mailing list for similar problems. Cheers, Edi. From sites at brynmosher.com Wed Apr 26 19:44:30 2006 From: sites at brynmosher.com (sites at brynmosher.com) Date: Wed, 26 Apr 2006 12:44:30 -0700 Subject: [regex-coach] problem with dot '.' inside brackets Message-ID: <20060426194300.B5E4C7A00D@common-lisp.net> I've been using Regex-Coach 0.8.4 on Windows to test some SpamAssassin rules and noticed something odd: Placing the following expression: [.|m] to match the following data: bleh.com Matches the '.' in bleh.com and not the first non-linefeed character as the '.' character in the expression should match. It's almost as if I had excaped the '.' like '\.'. Using the expression '[.]' yields the same result. I've also noticed that the non-match character '^' doesn't work inside brackets as well. Is this an error or am I crazy? Bryn From edi at agharta.de Wed Apr 26 21:17:25 2006 From: edi at agharta.de (Edi Weitz) Date: Wed, 26 Apr 2006 23:17:25 +0200 Subject: [regex-coach] problem with dot '.' inside brackets In-Reply-To: <20060426194300.B5E4C7A00D@common-lisp.net> (sites@brynmosher.com's message of "Wed, 26 Apr 2006 12:44:30 -0700") References: <20060426194300.B5E4C7A00D@common-lisp.net> Message-ID: On Wed, 26 Apr 2006 12:44:30 -0700, sites at brynmosher.com wrote: > I've been using Regex-Coach 0.8.4 on Windows to test some > SpamAssassin rules and noticed something odd: > > Placing the following expression: > [.|m] > > to match the following data: > bleh.com > > Matches the '.' in bleh.com and not the first non-linefeed character > as the '.' character in the expression should match. It's almost as > if I had excaped the '.' like '\.'. Using the expression '[.]' > yields the same result. I've also noticed that the non-match > character '^' doesn't work inside brackets as well. > > Is this an error or am I crazy? Well, at least it's not an error... :) Most characters that have a special meaning in regular expressions (like the dot or the pipe symbol, for example) are treated like normal characters within character classes, i.e. within square brackets. See 'man perlre' for details. BTW, it seems that your understanding of character classes as a whole is wrong. If the dot /would/ match every non-linefeed character, then "[.|m]" would be equivalent to "[.]". Cheers, Edi. From sites at brynmosher.com Wed Apr 26 21:41:09 2006 From: sites at brynmosher.com (sites at brynmosher.com) Date: Wed, 26 Apr 2006 14:41:09 -0700 Subject: [regex-coach] problem with dot '.' inside brackets Message-ID: <20060426213134.B8DC45D095@common-lisp.net> the "|m" was just in there for the example. I'm actually trying to match html tags with small contents inside like; V I A G R A with the expression similar to "/(>.{1,4}<[\S\s]*){4}/" and noticed the behaviour when I changed the ".{1,4}" to "[.^<]{1,4}". I did notice that "\s" and "\S" are matched inside a character class, which is what I think led me to assume other meta-characters would be too. I've only been using regex for a while, so I am stumbling along. Thanks for the man page. I'm reading it now. Any other advice you could give for this expression would be great. Thanks, Bryn ----- Original Message ----- From: Edi Weitz To: sites at brynmosher.com Cc: regex-coach at common-lisp.net Date: Wed, 26 Apr 2006 23:17:25 +0200 Subject: Re: [regex-coach] problem with dot '.' inside brackets > On Wed, 26 Apr 2006 12:44:30 -0700, sites at brynmosher.com wrote: > > > I've been using Regex-Coach 0.8.4 on Windows to test some > > SpamAssassin rules and noticed something odd: > > > > Placing the following expression: > > [.|m] > > > > to match the following data: > > bleh.com > > > > Matches the '.' in bleh.com and not the first non-linefeed character > > as the '.' character in the expression should match. It's almost as > > if I had excaped the '.' like '\.'. Using the expression '[.]' > > yields the same result. I've also noticed that the non-match > > character '^' doesn't work inside brackets as well. > > > > Is this an error or am I crazy? > > Well, at least it's not an error... :) > > Most characters that have a special meaning in regular expressions > (like the dot or the pipe symbol, for example) are treated like normal > characters within character classes, i.e. within square brackets. > > See 'man perlre' for details. > > BTW, it seems that your understanding of character classes as a whole > is wrong. If the dot /would/ match every non-linefeed character, then > "[.|m]" would be equivalent to "[.]". > > Cheers, > Edi. > From era+regex=coach at iki.fi Thu Apr 27 12:56:49 2006 From: era+regex=coach at iki.fi (era+regex=coach at iki.fi) Date: Thu, 27 Apr 2006 15:56:49 +0300 Subject: [regex-coach] problem with dot '.' inside brackets In-Reply-To: <20060426213134.B8DC45D095@common-lisp.net> References: <20060426213134.B8DC45D095@common-lisp.net> Message-ID: <1146142609.11876.260069851@webmail.messagingengine.com> On Wed, 26 Apr 2006 14:41:09 -0700, sites at brynmosher.com said: > I'm actually trying to match html tags with small contents inside like; > V > with the expression similar to "/(>.{1,4}<[\S\s]*){4}/" and noticed the > behaviour when I changed the ".{1,4}" to "[.^<]{1,4}". This also explains your comment about ^ not working. It needs to be first in the character class, like [^.<] But actually, I'm guessing your real problem is with the greediness of the * operator, which would skip over as much as possible, and that is why you have artificially constrained it with the {1,4} to only match a few characters. What you're actually looking for, then, is "a > followed by anything except <", i.e. >[^<]*, yielding /(>[^<]*<[^>]*){4}/ ... or even, in Perl-compatible regular expressions, the non-greedy *?, but that is a bit hard to apply here without more knowledge of what you are actually trying to match. (I still don't understand the significance of the final {4}, for example. Or maybe you were meaning to say <.{1,4} but applying the repeat to the wrong scope?) Hope this helps, /* era */ -- If this were a real .signature, it would suck less. Well, maybe not. From edi at agharta.de Thu Apr 27 19:16:26 2006 From: edi at agharta.de (Edi Weitz) Date: Thu, 27 Apr 2006 21:16:26 +0200 Subject: [regex-coach] Re: regex-coah and FC5 In-Reply-To: <4451064C.50308@gaetanlord.ca> (Gaetan Lord's message of "Thu, 27 Apr 2006 13:58:36 -0400") References: <4451064C.50308@gaetanlord.ca> Message-ID: [Please use the mailing list.] On Thu, 27 Apr 2006 13:58:36 -0400, Gaetan Lord wrote: > I tried your software with Fedora Core 5. FC5 ship with openmotif > 2.3, and I can't get your software starting with it. > libXm.so.2: cannot open shared object file: No such file or directory. > > I tried to symlink libXm.so.4 to it but I get thye following message > Error: Motif version string ("@(#)Motif Version 2.3.0") indicates > invalid library version. Requires (("Lesstif" "2.1") ("Motif" > "2.2")). > > Any chance you will have a version compiled with a newer motif. This will most likely happen once I have the new LispWorks compiler which is due to be released in the next months. Cheers, Edi. From edi at agharta.de Fri Apr 28 15:27:23 2006 From: edi at agharta.de (Edi Weitz) Date: Fri, 28 Apr 2006 17:27:23 +0200 Subject: [regex-coach] New version 0.8.5 Message-ID: ChangeLog: Version 0.8.5 2006-04-28 Correct state of highlight buttons and messages when app starts up (caught by Shmuel Zeigerman) Download: [Windows] [Linux, FreeBSD] Cheers, Edi.