From xemacs-m  Sat Mar 15 00:37:00 1997
Received: from mecca.spd.louisville.edu (mecca.spd.louisville.edu [136.165.40.148])
	by xemacs.org (8.8.5/8.8.5) with SMTP id AAA15420
	for <xemacs-beta@xemacs.org>; Sat, 15 Mar 1997 00:36:58 -0600 (CST)
Received: (from tjchol01@localhost) by mecca.spd.louisville.edu (950413.SGI.8.6.12/8.6.12) id GAA08610; Sat, 15 Mar 1997 06:37:05 GMT
Date: Sat, 15 Mar 1997 06:37:05 GMT
Message-Id: <199703150637.GAA08610@mecca.spd.louisville.edu>
From: "Tomasz J. Cholewo" <tjchol01@mecca.spd.louisville.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: XEmacs-Beta Mailing List <xemacs-beta@xemacs.org>
Subject: Re: Lisp font-lock keywords?
In-Reply-To: <rv7mjamenn.fsf@sdnp5.ucsd.edu>

David Moore wrote:
> all-completions is returning everything rather than just the single
> character items.  I think I saw someone mail a patch for this out a
> couple weeks ago, but it looks like it didn't make it into the current
> betas.  Does someone have this fix?

The fix (which I posted originally on March 10th) will be incorporated
in the betas scheduled for Saturday.  Just in case someone needs it
Right Now:

diff -urd xemacs-20.1-b6-orig/src/minibuf.c xemacs-20.1-b6/src/minibuf.c
--- xemacs-20.1-b6-orig/src/minibuf.c	Sat Jan 11 15:14:45 1997
+++ xemacs-20.1-b6/src/minibuf.c	Sun Mar  9 22:42:10 1997
@@ -232,7 +232,7 @@
 	  Lisp_Object re = XCAR (regexps);
 	  if (STRINGP (re)
 	      && (fast_string_match (re, nonreloc, reloc, offset,
-				     length, 0, ERROR_ME, 0) >= 0))
+				     length, 0, ERROR_ME, 0) < 0))
 	    return (1);
 	}
     }

