regexp bug?

regexp bug?

[coriordan]

hello.

I think I have found a bug in Emacs.  I was searching
for sentences that were separated with only one space
so I used the regexp search with "\. [^ ]".  My
search kept matching sentences with two spaces.
The minibuffer was showing my regexp as "\.\s-+[^ ]".

Hope I'm not missing something, please CC me if there
is any discussion as I am not on this list.

Thanks.
Ciaran O'Riordan

Re: regexp bug?

[Juanma Barranquero]

On Fri, 13 Sep 2002 10:05:51 +0100, coriordan@compsoc.com wrote:

> I was searching
> for sentences that were separated with only one space
> so I used the regexp search with "\. [^ ]".  My
> search kept matching sentences with two spaces.
> The minibuffer was showing my regexp as "\.\s-+[^ ]".

I bet that happened while you used `isearch-forward-regexp'.

Please check the docstring of the variable `search-whitespace-regexp'.


                                                           /L/e/k/t/u

Re: regexp bug?

[coriordan]

On Fri, Sep 13, 2002 at 11:30:45AM +0200, Juanma Barranquero wrote:
> 
> > I was searching[...]
> 
> I bet that happened while you used `isearch-forward-regexp'.
> 
> Please check the docstring of the variable `search-whitespace-regexp'.

oh, it's a feature ;)

sorry for my laziness, thanks.

Ciaran O'Riordan

Re: regexp bug?

[Juanma Barranquero]

On Fri, 13 Sep 2002 11:47:37 +0100, coriordan@compsoc.com wrote:

> oh, it's a feature ;)

That I didn't know, I found it while researching your bug report.

> sorry for my laziness, thanks.

No problem.

BTW, I you don't know already, I'll suggest taking a look into
`highlight-lines-matching-regexp' (from hi-lock.el), `occur' and
`re-builder'. Very handy.


                                                           /L/e/k/t/u

regexp bug?

[David Abrahams]

If I put point on a letter, like this "x", (looking-at " *") returns t
but (looking-at "\s *") returns nil.

Is that intended?  Is it documented?

Thanks in advance,

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com

Re: regexp bug?

[David Abrahams]

David Abrahams <dave@boost-consulting.com> writes:

> If I put point on a letter, like this "x", (looking-at " *") returns t
> but (looking-at "\s *") returns nil.
>
> Is that intended?  Is it documented?

Gah!  Sorry, missing the double backslash!

Nevermind.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com

Re: regexp bug?

[Kim F. Storm]

David Abrahams <dave@boost-consulting.com> writes:

> If I put point on a letter, like this "x", (looking-at " *") returns t
> but (looking-at "\s *") returns nil.

Try (looking-at "\\s *") 

-- 
Kim F. Storm  http://www.cua.dk

Re: regexp bug?

[David Kastrup]

David Abrahams <dave@boost-consulting.com> writes:

> If I put point on a letter, like this "x", (looking-at " *") returns t
> but (looking-at "\s *") returns nil.
>
> Is that intended?  Is it documented?

Yes.  But in

(info "(elisp) Syntax for Strings")

instead of

(info "(elisp) Syntax of Regexps")

since

(looking-at "\s *") is the same as (looking-at "s *"),

You probably want (looking-at "\\s *") instead.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: regexp bug?

[Kim F. Storm]

David Kastrup <dak@gnu.org> writes:

> (looking-at "\s *") is the same as (looking-at "s *"),

In emacs 22, it is the same as (looking-at "  *"),

-- 
Kim F. Storm  http://www.cua.dk