bug#21279: 24.4; (match-end 0) doesn't always return nil when previous s

bug-gnu-emacs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#21279: 24.4; (match-end 0) doesn't always return nil when previous s

From:	Andreas Schwab
Subject:	bug#21279: 24.4; (match-end 0) doesn't always return nil when previous string-match fails
Date:	Mon, 17 Aug 2015 09:26:39 +0200
User-agent:	Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)

Ernesto Alfonso <erjoalgo@gmail.com> writes:

> (match-end 0) doesn't always return nil when previous string-match fails:

A failing match doesn't set match-data.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

[Prev in Thread]

Current Thread

[Next in Thread]

bug#21279: 24.4; (match-end 0) doesn't always return nil when previous string-match fails, Ernesto Alfonso, 2015/08/17
- bug#21279: 24.4; (match-end 0) doesn't always return nil when previous string-match fails, Andreas Schwab <=
  - bug#21279: 24.4; (match-end 0) doesn't always return nil when previous string-match fails, Ernesto Alfonso, 2015/08/17
- bug#21279: 24.4; (match-end 0) doesn't always return nil when previous string-match fails, Paul Eggert, 2015/08/18

Prev by Date: bug#21277: 25.0.50; char-fold search is a screw, and I can't see how to disable
Next by Date: bug#21279: 24.4; (match-end 0) doesn't always return nil when previous string-match fails
Previous by thread: bug#21279: 24.4; (match-end 0) doesn't always return nil when previous string-match fails
Next by thread: bug#21279: 24.4; (match-end 0) doesn't always return nil when previous string-match fails
Index(es):
- Date
- Thread