From xemacs-m  Wed Sep  3 13:03:10 1997
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by xemacs.org (8.8.5/8.8.5) with SMTP id NAA12797
	for <xemacs-beta@xemacs.org>; Wed, 3 Sep 1997 13:03:08 -0500 (CDT)
Received: from Corp.Sun.COM ([129.145.35.78]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id LAA20491 for <xemacs-beta@xemacs.org>; Wed, 3 Sep 1997 11:02:15 -0700
Received: from legba.Corp.Sun.COM by Corp.Sun.COM (SMI-8.6/SMI-5.3)
	id LAA14956; Wed, 3 Sep 1997 11:02:11 -0700
Received: by legba.Corp.Sun.COM (SMI-8.6/SMI-SVR4)
	id LAA08068; Wed, 3 Sep 1997 11:02:14 -0700
To: xemacs-beta@xemacs.org
Subject: Invalid preceding regular expression
X-Attribution: GDF
Mail-Copies-To: never
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
From: Gary.Foster@Corp.Sun.COM (Gary D. Foster)
Date: 03 Sep 1997 11:02:14 -0700
Message-ID: <bcirab6b7ix.fsf@corp.Sun.COM>
Lines: 16
X-Mailer: Gnus v5.4.65/XEmacs 20.3(beta19) - "Kyiv"

The new regex patches broke my GNUS crossposting spam filter.  I have
the following in my SCORE file for Gnus, version 5.4.65:

("xref"
  ("[^:\n]+:[0-9]+ +[^:\n]+:[0-9]++[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+" -700 nil r))

Which worked fine under 20.3-b18.  However, with Kyiv, The above gives 
me "Invalid preceding regular expression" on this rule.

Is this right, or wrong?  I thought the regex patches weren't supposed 
to break anything, only add functionality?  I pretty much ignored the
regex debate because I wasn't real interested in it, and I apologize
for being blithely unaware.  Maybe I'd better start paying better
attention...

-- Gary F.

