# HG changeset patch
# User Jim Blandy <jimb@redhat.com>
# Date 742976740 0
# Node ID 42faad1466fa70978b04236b1825b986e5bdc557
# Parent  9f3fe01a678d8b9a99b2bd854f4d712ecf620107
	* keyboard.c (read_key_sequence): Accept both strings and vectors
	as bindings in function-key-map.
    	* keymap.c (Vfunction_key_map in syms_of_keymap): Doc fix.

	* keymap.c (syms_of_keymap): Doc fix.

diff -r 9f3fe01a678d -r 42faad1466fa src/keymap.c
--- a/src/keymap.c	Sun Jul 18 06:25:09 1993 +0000
+++ b/src/keymap.c	Sun Jul 18 06:25:40 1993 +0000
@@ -2243,14 +2243,14 @@
 The read-key-sequence function replaces subsequences bound by\n\
 function-key-map with their bindings.  When the current local and global\n\
 keymaps have no binding for the current key sequence but\n\
-function-key-map binds a suffix of the sequence to a vector,\n\
+function-key-map binds a suffix of the sequence to a vector or string,\n\
 read-key-sequence replaces the matching suffix with its binding, and\n\
 continues with the new sequence.\n\
 \n\
-For example, suppose function-key-map binds `ESC O P' to [pf1].\n\
-Typing `ESC O P' to read-key-sequence would return [pf1].  Typing\n\
-`C-x ESC O P' would return [?\C-x pf1].  If [pf1] were a prefix\n\
-key, typing `ESC O P x' would return [pf1 x].");
+For example, suppose function-key-map binds `ESC O P' to [f1].\n\
+Typing `ESC O P' to read-key-sequence would return [f1].  Typing\n\
+`C-x ESC O P' would return [?\\C-x f1].  If [f1] were a prefix\n\
+key, typing `ESC O P x' would return [f1 x].");
   Vfunction_key_map = Fmake_sparse_keymap (Qnil);
 
   Qsingle_key_description = intern ("single-key-description");