nano

commit a849ab12eab6c12d74c3228ab39f900589475c98
parent 0381c2199dcea2a5ae0aeed85540b16b820d68a5
Author: David Lawrence Ramsey <pooka109@gmail.com>
Date:   Sat,  1 May 2004 04:13:06 +0000

fix minor inconsistency


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@1726 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

Diffstat:
M
src/winio.c
 | 
8
++++----

1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/winio.c b/src/winio.c
@@ -46,14 +46,14 @@ static int statblank = 0;	/* Number of keystrokes left after
  *   VT220, and VT320.
  * - NANO_XOFF_KEY is Ctrl-S, which is XOFF under ASCII, ANSI, VT100,
  *   VT220, and VT320.
- * - NANO_CONTROL_8 is Ctrl-? (Ctrl-8), which is Delete under ASCII,
+ * - NANO_CONTROL_8 is Ctrl-8 (Ctrl-?), which is Delete under ASCII,
  *   ANSI, VT100, and VT220, and which is Backspace under VT320.
  *
  * Note: VT220s and VT320s also generate Esc [ 3 ~ for Delete.  By
- * default, xterm assumes it's running on a VT320 and generates Ctrl-?
- * (Ctrl-8) for Backspace and Esc [ 3 ~ for Delete.  This causes
+ * default, xterm assumes it's running on a VT320 and generates Ctrl-8
+ * (Ctrl-?) for Backspace and Esc [ 3 ~ for Delete.  This causes
  * problems for VT100-derived terminals such as the FreeBSD console,
- * which expect Ctrl-H for Backspace and Ctrl-? (Ctrl-8) for Delete, and
+ * which expect Ctrl-H for Backspace and Ctrl-8 (Ctrl-?) for Delete, and
  * on which the VT320 sequences are translated by the keypad to KEY_DC
  * and [nothing].  We work around this conflict via the REBIND_DELETE
  * flag: if it's not set, we assume VT320 compatibility, and if it is,