|
|
|
|
|
|
|
naries), except that all entries beginning with nonalphabetic characters are sorted after Z. The case-blindness is a feature, not a bug. |
|
|
|
|
|
|
|
|
Jargon terms with entries in the file are boldfaced. This isn't done all the time for every such word, but it is done everywhere that a reminder seems useful that the term has a jargon meaning and one might wish to refer to its entry. |
|
|
|
|
|
|
|
|
Defining instances of terms and phrases appear in italic type. A defining instance is one which occurs near to or as part of an explanation of it. |
|
|
|
|
|
|
|
|
Prefixed ** is used as linguists do; to mark examples of incorrect usage. |
|
|
|
|
|
|
|
|
We follow the 'logical' quoting convention described in the Writing Style section above. In addition, we reserve double quotes for actual excerpts of text or (sometimes invented) speech. Scare quotes (which mark a word being used in a nonstandard way), and philosopher's quotes (which turn an utterance into the string of letters or words that name it) are both rendered with single quotes. |
|
|
|
|
|
|
|
|
References such as malloc(3) and patch(1) are to Unix facilities (some of which, such as patch(1), are actually freeware distributed over Usenet). The Unix manuals use foo(n) to refer to item foo in section (n) of the manual, where n = 1 is utilities, n = 2 is system calls, n = 3 is C library routines, n = 6 is games, and n = 8 (where present) is system administration utilities. Sections 4, 5, and 7 of the manuals have changed roles frequently and in any case are not referred to in any of the entries. |
|
|
|
|
|
|
|
|
Various abbreviations used frequently in the lexicon are summarized here: |
|
|
|
|
|