Mercurial > hg > xemacs-beta
annotate man/lispref/back.texi @ 5634:2014ff433daf
Support hash COLLECTIONs, #'{all,try}-completion{s,}; add #'test-completion
src/ChangeLog addition:
2012-01-01 Aidan Kehoe <kehoea@parhasard.net>
Add #'test-completion, API from GNU.
Accept hash table COLLECTIONs in it and in the other
completion-oriented functions, #'try-completion,
#'all-completions, and those Lisp functions implemented in terms
of them.
* lisp.h: Update the prototype of map_obarray(), making FN
compatible with the FUNCTION argument of elisp_maphash();
* abbrev.c (abbrev_match_mapper):
* abbrev.c (record_symbol):
* doc.c (verify_doc_mapper):
* symbols.c (mapatoms_1):
* symbols.c (apropos_mapper):
Update these mapper functions to reflect the new argument to
map_obarray().
* symbols.c (map_obarray):
Call FN with two arguments, the string name of the symbol, and the
symbol itself, for API (mapper) compatibility with
elisp_maphash().
* minibuf.c (map_completion): New. Map a maphash_function_t across
a non function COLLECTION, as appropriate for #'try-completion and
friends.
* minibuf.c (map_completion_list): New. Map a maphash_function_t
across a pseudo-alist, as appropriate for the completion
functions.
* minibuf.c (ignore_completion_p): PRED needs to be called with
two args if and only if the collection is a hash table. Implement
this.
* minibuf.c (try_completion_mapper): New. The loop body of
#'try-completion, refactored out.
* minibuf.c (Ftry_completion): Use try_completion_mapper(),
map_completion().
* minibuf.c (all_completions_mapper): New. The loop body of
#'all-completions, refactored out.
* minibuf.c (Fall_completions): Use all_completions_mapper(),
map_completion().
* minibuf.c (test_completion_mapper): New. The loop body of
#'test-completion.
* minibuf.c (Ftest_completion): New, API from GNU.
* minibuf.c (syms_of_minibuf): Make Ftest_completion available.
tests/ChangeLog addition:
2012-01-01 Aidan Kehoe <kehoea@parhasard.net>
* automated/completion-tests.el: New.
Test #'try-completion, #'all-completion and #'test-completion with
list, vector and hash-table COLLECTION arguments.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Sun, 01 Jan 2012 15:18:52 +0000 |
parents | 3ecd8885ac67 |
children |
rev | line source |
---|---|
428 | 1 \input /home/gd/gnu/doc/texinfo.tex @c -*-texinfo-*- |
2 @c %**start of header | |
3 @setfilename ../../info/back-cover | |
4 @settitle XEmacs Lisp Reference Manual | |
5 @c %**end of header | |
6 . | |
7 @sp 7 | |
8 @center @titlefont {XEmacs Lisp} | |
9 @sp 1 | |
10 | |
11 @quotation | |
12 Most of the XEmacs text editor is written in the programming | |
13 language called XEmacs Lisp. You can write new code in XEmacs Lisp and | |
14 install it as an extension to the editor. However, XEmacs Lisp is more | |
15 than a mere ``extension language''; it is a full computer programming | |
16 language in its own right. You can use it as you would any other | |
17 programming language. | |
18 | |
19 Because XEmacs Lisp is designed for use in an editor, it has special | |
20 features for scanning and parsing text as well as features for handling | |
21 files, buffers, displays, subprocesses, and so on. XEmacs Lisp is | |
22 closely integrated with the editing facilities; thus, editing commands | |
23 are functions that can also conveniently be called from Lisp programs, | |
24 and parameters for customization are ordinary Lisp variables. | |
25 | |
26 This manual describes XEmacs Lisp. Generally speaking, the earlier | |
27 chapters describe features of XEmacs Lisp that have counterparts in | |
28 many programming languages, and later chapters describe features that | |
29 are peculiar to XEmacs Lisp or relate specifically to editing. | |
30 @end quotation | |
31 | |
32 @hfil | |
33 @bye |