Mercurial > hg > xemacs-beta
annotate tests/automated/README @ 5872:f9e59cd39a9a
Clean up #'read-quoted-char, support help-event-list there.
lisp/changeLog addition:
2015-03-14 Aidan Kehoe <kehoea@parhasard.net>
* simple.el (quoted-insert):
Update the docstring here, syncing GNU's, especially mentioning
read-quoted-char-radix.
* cmdloop.el:
* cmdloop.el (read-quoted-char-radix): Move this up here, outside
the functions.
* cmdloop.el (read-function-key-map): New label, reading and
replacing characters from function-key-map if appropriate.
* cmdloop.el (read-quoted-char): Multiple changes:
-- Take advantage of help-event-list, but be careful not to have
any keystrokes with character equivalents in it, so the user can
type C-q C-h and have the expected result.
-- Use function-key-map, as does #'read-char and
#'read-exclusive-char, helpful for character composition under
X11.
-- Pop up the help window ourselves if, e.g. F1 arrives on a TTY
via function-key-map, event-stream won't have done it.
-- Error if no keystroke that can be converted into a character is
specified, don't just insert ?\x00 as we used to and as does GNU
-- Use #'digit-char-p instead of reimplementing it.
-- Fix a bug of mine where I wasn't consistent about treating
character codes as Unicode.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Tue, 17 Mar 2015 12:22:50 +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'. |