From owner-freebsd-questions Sat Oct 17 01:19:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13736 for freebsd-questions-outgoing; Sat, 17 Oct 1998 01:19:06 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from phoenix.welearn.com.au (suebla.lnk.telstra.net [139.130.44.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13720 for ; Sat, 17 Oct 1998 01:19:00 -0700 (PDT) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.9.1/8.9.0) id SAA26156; Sat, 17 Oct 1998 18:18:35 +1000 (EST) Message-ID: <19981017181831.30783@welearn.com.au> Date: Sat, 17 Oct 1998 18:18:31 +1000 From: Sue Blake To: freebsd-questions@FreeBSD.ORG Subject: enter doesn't work Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sometimes when I telnet in and use mutt, mutt complains that the enter key (or return) is an unknown key ("key not bound"). When this happened from windoze systems I thought nothing of it. Last night I was using FreeBSD 2.2.7, telnetting to FreeBSD 2.2.2 where mutt lives. Neither machine has an owner knowledgeable enough to have changed anything more complex than installing bash. 'echo $TERM' comes back cons25 on both machines. I logged in several times and still couldn't use the enter key within mutt (i.e. could list mail but not read it). Other keys worked in mutt, and the enter key worked at the bash prompt. I tried from an xterm and still no go. Finally I ran screen on the remote system before running mutt, and that worked. Problem solved, but a mystery remains. Any clues? -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message