Mercurial > hg > xemacs-beta
annotate man/internals/index.texi @ 1333:1b0339b048ce
[xemacs-hg @ 2003-03-02 09:38:37 by ben]
To: xemacs-patches@xemacs.org
PROBLEMS: Include nt/PROBLEMS and update. Add note about incremental
linking badness.
cmdloop.el, custom.el, dumped-lisp.el, files.el, keydefs.el, keymap.el, lisp-mode.el, make-docfile.el, replace.el, simple.el, subr.el, view-less.el, wid-edit.el: Lots of syncing with FSF 21.2.
Use if-fboundp in wid-edit.el.
New file newcomment.el from FSF.
internals/internals.texi: Fix typo.
(Build-Time Dependencies): New node.
PROBLEMS: Delete.
config.inc.samp, xemacs.mak: Eliminate HAVE_VC6, use SUPPORT_EDIT_AND_CONTINUE in its place.
No incremental linking unless SUPPORT_EDIT_AND_CONTINUE, since it
can cause nasty crashes in pdump. Put warnings about this in
config.inc.samp. Report the full compile flags used for src
and lib-src in the Installation output.
alloc.c, lisp.h, ralloc.c, regex.c: Use ALLOCA() in regex.c to avoid excessive stack allocation.
Also fix subtle problem with REL_ALLOC() -- any call to malloc()
(direct or indirect) may relocate rel-alloced data, causing
buffer text to shift. After any such call, regex must update
all its pointers to such data. Add a system, when
ERROR_CHECK_MALLOC, whereby regex.c indicates all the places
it is prepared to handle malloc()/realloc()/free(), and any
calls anywhere in XEmacs outside of this will trigger an abort.
alloc.c, dialog-msw.c, eval.c, event-stream.c, general-slots.h, insdel.c, lisp.h, menubar-msw.c, menubar-x.c: Change *run_hook*_trapping_problems to take a warning class, not
a string. Factor out code to issue warnings, add flag to
call_trapping_problems() to postpone warning issue, and make
*run_hook*_trapping_problems issue their own warnings tailored
to the hook, postponed in the case of safe_run_hook_trapping_problems()
so that the appropriate message can be issued about resetting to
nil only when not `quit'. Make record_unwind_protect_restoring_int()
non-static.
dumper.c: Issue notes about incremental linking problems under Windows.
fileio.c: Mule-ize encrypt/decrypt-string code.
text.h: Spacing changes.
author | ben |
---|---|
date | Sun, 02 Mar 2003 09:38:54 +0000 |
parents | 1ccc32a20af4 |
children |
rev | line source |
---|---|
398 | 1 @c -*-texinfo-*- |
2 @setfilename ../../info/index.info | |
3 | |
4 @c Indexing guidelines | |
5 | |
6 @c I assume that all indexes will be combined. | |
7 @c Therefore, if a generated findex and permutations | |
8 @c cover the ways an index user would look up the entry, | |
9 @c then no cindex is added. | |
10 @c Concept index (cindex) entries will also be permuted. Therefore, they | |
11 @c have no commas and few irrelevant connectives in them. | |
12 | |
13 @c I tried to include words in a cindex that give the context of the entry, | |
14 @c particularly if there is more than one entry for the same concept. | |
15 @c For example, "nil in keymap" | |
16 @c Similarly for explicit findex and vindex entries, e.g. "print example". | |
17 | |
18 @c Error codes are given cindex entries, e.g. "end-of-file error". | |
19 | |
20 @c pindex is used for .el files and Unix programs | |
21 | |
446 | 22 @node Index, , Interface to the X Window System, Top |
398 | 23 @unnumbered Index |
24 | |
25 @ignore | |
26 All variables, functions, keys, programs, files, and concepts are | |
27 in this one index. | |
28 | |
29 All names and concepts are permuted, so they appear several times, one | |
30 for each permutation of the parts of the name. For example, | |
31 @code{function-name} would appear as @b{function-name} and @b{name, | |
32 function-}. Key entries are not permuted, however. | |
33 @end ignore | |
34 | |
35 @c Print the indices | |
36 | |
37 @printindex fn |