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:	npostavs
Subject:	bug#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!)
Date:	Sun, 07 Aug 2016 10:27:37 -0400
User-agent:	Gnus/5.13 (Gnus v5.13) Emacs/25.0.93 (gnu/linux)

tags 24166 fixed
close 24166 25.2
quit

Pushed as 7fb75680

[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?!), 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?!), 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 <=
    - 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/07
    - 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#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!)
Next by Date: bug#24171: 25.1; Bytecode returns nil instead of expected closure
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#24166: With --eval, errors in string-match-p do not produce backtraces (but errors in string-match do?!)
Index(es):
- Date
- Thread