bug#24166: With --eval, errors in string-match-p do not produce backtrac

bug-gnu-emacs

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

bug#24166: With --eval, errors in string-match-p do not produce backtrac

From:	Clément Pit--Claudel
Subject:	bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!)
Date:	Sun, 7 Aug 2016 11:43:42 -0400
User-agent:	Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0

On 2016-08-07 10:27, npostavs@users.sourceforge.net wrote:
> tags 24166 fixed
> close 24166 25.2
> quit
> 
> Pushed as 7fb75680

Yay! Thanks everyone :)

signature.asc
Description: OpenPGP digital signature

[Prev in Thread]

Current Thread

[Next in Thread]

bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), (continued)
- bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), npostavs, 2016/08/05
  - bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), Clément Pit--Claudel, 2016/08/05
  - bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), Eli Zaretskii, 2016/08/06
    - bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), Noam Postavsky, 2016/08/06
    - bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), Eli Zaretskii, 2016/08/06
    - bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), Noam Postavsky, 2016/08/06
    - bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), Eli Zaretskii, 2016/08/06
    - bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), npostavs, 2016/08/06
    - bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), Eli Zaretskii, 2016/08/07
    - bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), npostavs, 2016/08/07
    - bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!), Clément Pit--Claudel <=
    - Message not available
    - Message not available
    - bug#23949: acknowledged by developer (Re: bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!)), Kaushal Modi, 2016/08/09

Prev by Date: bug#24171: 25.1; Bytecode returns nil instead of expected closure
Next by Date: bug#7070: `load-time-value' local-vars this-kind and that-one
Previous by thread: bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!)
Next by thread: bug#23949: acknowledged by developer (Re: bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!))
Index(es):
- Date
- Thread