GNU bug report logs - #20806
25.0.50; `string-match' is confused???

Previous Next

Full log

Message #11 received at 20806 <at> debbugs.gnu.org (full text, mbox):

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Vaidheeswaran C <vaidheeswaran.chinnaraju <at> gmail.com>
Cc: 20806 <at> debbugs.gnu.org
Subject: Re: bug#20806: 25.0.50;  `string-match' is confused???
Date: Sun, 14 Jun 2015 00:58:23 +0200

Vaidheeswaran C <vaidheeswaran.chinnaraju <at> gmail.com> writes:

> Debugger entered--Lisp error: (error "Regexp cannot match an empty
> string")
>   signal(error ("Regexp cannot match an empty string"))
>   error("Regexp cannot match an empty string")
>  [...]
>   command-execute(highlight-regexp)

AFAICT, you got this error because you entered an regexp to the
`highlight-regexp' prompt that the empty string is matched by.  Such a
regexp is rejected by hi-lock.  With other words, the error is raised by
intent in hi-lock.el.

I guess, theoretically this rejected case could be made working, but the
code would get a bit uglier and less effective then, and is easy to
avoid.

What's your use case?


Michael.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.