# HG changeset patch
# User Eric S. Raymond <esr@snark.thyrsus.com>
# Date 732576099 0
# Node ID 8d18b4730895f0f3c8aeedf6fe6b5e160d12e470
# Parent  1e0291fca151dd248cba3bce3bf8afb6b1f9c05f
Info on the terminal-package-finding algorithm.

diff -r 1e0291fca151 -r 8d18b4730895 lisp/term/README
--- a/lisp/term/README	Fri Mar 19 21:03:48 1993 +0000
+++ b/lisp/term/README	Fri Mar 19 21:21:39 1993 +0000
@@ -1,14 +1,21 @@
    This directory contains files of elisp that customize Emacs for certain
-terminal types.  When Emacs starts, it checks the TERM environment variable to
-see what type of terminal the user is running on, checks for an elisp file
-named "term/${TERM}.el", and if one exists, loads it.
+terminal types.
+
+   When Emacs starts, it checks the TERM environment variable to see what type
+of terminal the user is running on, checks for an elisp file named
+"term/${TERM}.el", and if one exists, loads it.  If that doesn't yield a file
+that exists, the last hyphen and what follows it is stripped.  If that doesn't
+yield a file that exists, the previous hyphen is stripped, and so on until all
+hyphens are gone.  For example, if the terminal type is `aaa-48-foo', Emacs
+will try first `term/aaa-48-foo.el', then `term/aaa-48.el' and finally
+`term/aaa.el'.
 
    When writing terminal packages, there are some things it is good to keep in
 mind.
 
    First, about keycap names.  Your terminal package can create any keycap
 cookies it likes, but there are good reasons to stick to the set recognized by
-the X-windows code whenever possible.  The X key symbols recognized by Emacs
+the X-windows code whenever possible.  The key symbols recognized by Emacs
 are listed in src/term.c; look for the string `keys' in that file.
 
    For one thing, it means that you'll have the same Emacs key bindings on in