From owner-freebsd-bugs  Sat Apr  1 12:00:02 1995
Return-Path: bugs-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA27378 for bugs-outgoing; Sat, 1 Apr 1995 12:00:02 -0800
Received: (from gnats@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA27368; Sat, 1 Apr 1995 12:00:01 -0800
Date: Sat, 1 Apr 1995 12:00:01 -0800
Message-Id: <199504012000.MAA27368@freefall.cdrom.com>
From: J Wunsch <j@uriah.heep.sax.de>
Reply-To: J Wunsch <j@uriah.heep.sax.de>
To: freebsd-bugs
Subject: gnu/289: info(1) cannot handle arrow keys
In-Reply-To: Your message of Sat, 1 Apr 1995 21:46:00 +0200
	<199504011946.VAA21269@uriah.heep.sax.de>
Sender: bugs-owner@FreeBSD.org
Precedence: bulk


>Number:         289
>Category:       gnu
>Synopsis:       info(1) cannot handle arrow keys on a VT100
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs (FreeBSD bugs mailing list)
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Apr  1 12:00:01 1995
>Originator:     J Wunsch
>Organization:
>Release:        FreeBSD 2.1.0-Development i386
>Environment:


>Description:

info(1) beeps when being faced with the arrow keys as sent by a VT100-
compatible terminal.  This is not acceptable for a user-friendly front-
end to a substantial part of the system documentation (especially
considering the fact that emacs(1) *does* know how to handle it right
out of the box).

Users cannot be expected to now something about C-N and C-P just in
order to move the cursor around.

>How-To-Repeat:

Start info(1) from something that emulates a VT100 (pcvt(4), kermit(1)),
and hit an arrow key.

>Fix:
	

>Audit-Trail:
>Unformatted: