Mercurial > hg > xemacs-beta
annotate tests/automated/README @ 5855:0bddb59072b6
Look for cased character classes when deciding on case-fold-search, #'isearch
lisp/ChangeLog addition:
2015-03-11 Aidan Kehoe <kehoea@parhasard.net>
* isearch-mode.el:
* isearch-mode.el (isearch-fix-case):
Use the new #'no-case-regexp-p function if treating ISEARCH-STRING
as a regular expression; otherwise, use the [[:upper:]] character
class.
* isearch-mode.el (isearch-no-upper-case-p): Removed.
* isearch-mode.el (with-caps-disable-folding): Removed.
These two haven't been used since 1998.
* occur.el (occur-1):
Use #'no-case-regexp-p here.
* replace.el (perform-replace):
Don't use #'no-upper-case-p, use #'no-case-regexp-p or
(string-match "[[:upper:]]" ...) as appropriate.
* simple.el:
* simple.el (no-upper-case-p): Removed. This did two different
things, and its secondary function (examining regular expressions)
just became much more complicated; move the regular expression
functionality to its own function, use character classes when
examining non-regular-expressions instead.
The code to look for character classes, and the design decision
that this should be done, are from GNU, thank you Stefan Monnier.
* simple.el (no-case-regexp-p): New.
Given a REGEXP, return non-nil if it has nothing to suggest an
interactive user wants a case-sensitive search.
* simple.el (with-search-caps-disable-folding):
* simple.el (with-interactive-search-caps-disable-folding):
Update both these macros to use #'no-case-regexp-p.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Wed, 11 Mar 2015 18:06:15 +0000 |
parents | 74fd4e045ea6 |
children |
rev | line source |
---|---|
398 | 1 This directory contains XEmacs' automated test suite. The usual way |
2 of running all the tests is running `make check' from the top-level | |
3 source directory. | |
4 | |
5 The test suite is unfinished and it's still lacking some essential | |
6 features. It is nevertheless recommended that you run the tests to | |
7 confirm that XEmacs behaves correctly. | |
8 | |
9 If you want to run a specific test case, you can do it from the | |
10 command-line like this: | |
11 | |
12 $ xemacs -batch -l test-harness.elc -f batch-test-emacs TEST-FILE | |
13 | |
14 If something goes wrong, you can run the test suite interactively by | |
15 loading `test-harness.el' into a running XEmacs and typing | |
16 `M-x test-emacs-test-file RET <filename> RET'. You will see a log of | |
17 passed and failed tests, which should allow you to investigate the | |
18 source of the error and ultimately fix the bug. | |
19 | |
20 Adding a new test file is trivial: just create a new file here and it | |
21 will be run. There is no need to byte-compile any of the files in | |
22 this directory -- the test-harness will take care of any necessary | |
23 byte-compilation. | |
24 | |
25 Look at the existing test cases for the examples of coding test cases. | |
26 It all boils down to your imagination and judicious use of the macros | |
27 `Assert', `Check-Error', `Check-Error-Message', and `Check-Message'. |