view lispref/index.texi @ 64715:46d503c20412

(doctor-type-symbol): "?\ " -> "?\s". (**mad**, *debug*, *print-space*, *print-upcase*, abuselst, abusewords, account, afraidof, arerelated, areyou, bak, beclst, bother, bye, canyou, chatlst, continue, deathlst, describe, drnk, drugs, eliza-flag, elizalst, famlst, feared, fears, feelings-about, foullst, found, hello, history, howareyoulst, howdyflag, huhlst, ibelieve, improve, inter, isee, isrelated, lincount, longhuhlst, lover, machlst, mathlst, maybe, moods, neglst, obj, object, owner, please, problems, qlist, random-adjective, relation, remlst, repetitive-shortness, replist, rms-flag, schoollst, sent, sexlst, shortbeclst, shortlst, something, sportslst, stallmanlst, states, subj, suicide-flag, sure, things, thlst, toklst, typos, verb, want, whatwhen, whereoutp, whysay, whywant, zippy-flag, zippylst): Defvar at compile time.

@c -*-texinfo-*-
@setfilename ../info/index

@c Indexing guidelines

@c I assume that all indexes will be combinded.
@c Therefore, if a generated findex and permutations
@c cover the ways an index user would look up the entry,
@c then no cindex is added.
@c Concept index (cindex) entries will also be permuted.  Therefore, they
@c have no commas and few irrelevant connectives in them.

@c I tried to include words in a cindex that give the context of the entry,
@c particularly if there is more than one entry for the same concept.
@c For example, "nil in keymap"
@c Similarly for explicit findex and vindex entries, e.g. "print example".

@c Error codes are given cindex entries, e.g. "end-of-file error".

@c pindex is used for .el files and Unix programs

@node Index, New Symbols, Standard Hooks, Top
@unnumbered Index

@c Print the indices

@printindex fn