From owner-freebsd-questions Wed Dec 18 23:28:26 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35B9637B401 for ; Wed, 18 Dec 2002 23:28:24 -0800 (PST) Received: from loki.daboyz.org (adsl-66-125-181-9.dsl.snfc21.pacbell.net [66.125.181.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A41243EA9 for ; Wed, 18 Dec 2002 23:28:24 -0800 (PST) (envelope-from mike@loki.daboyz.org) Received: from localhost.daboyz.org ([127.0.0.1] helo=loki.daboyz.org) by loki.daboyz.org with esmtp (Exim 4.10) id 18Ov4q-0005fL-00 for freebsd-questions@freebsd.org; Wed, 18 Dec 2002 23:26:40 -0800 Received: (from mike@localhost) by loki.daboyz.org (8.12.6/8.12.6/Submit) id gBJ7QexE021782 for freebsd-questions@freebsd.org; Wed, 18 Dec 2002 23:26:40 -0800 (PST) Date: Wed, 18 Dec 2002 23:26:40 -0800 From: Michael Barrett To: freebsd-questions@freebsd.org Subject: aterm, screen, and backspace Message-ID: <20021219072640.GB21600@daboyz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Howdy, I just recently got into freebsd and everything has been running great. Tonight I decided to change the compile time options that I set aterm up with and ran into some problems. Before doing this I went ahead and ran cvsup to make sure I had the latest and greatest port of aterm. I don't know if anything got updated, but I only built my machine about a month ago with the latest ports. I haven't seen any changes to the aterm port, but maybe I'm using the port changes search engine wrong. Anyways, after making sure I had the latest port info I then de-installed my copy of aterm, and then did a make install clean to re-install it, using the standard Makefile. Everything seemed fine till I went and ran screen. When I ran screen, I found that I could no longer use backspace. Instead of backspacing, it would instead simply cause my terminal to beep. I hit ^V then the backspace key and this is the code it's returning: ^[[3~ . I looked around the newsgroups and couldn't find a whole lot of answers in regards to this. I found something about .inputrc, a file which I use to give me vi bindings in the python interpreter. Here's the extent of my .inputrc file: set editing-mode vi I wouldn't imagine this would cause many problems, yet when I went ahead and moved the .inputrc to .inputrc.old and started up screen, then my backspace key printed a ~ and would cause my terminal to beep. Hitting ^V backspace now reported ^[[3~ as well. Anyways I quite plainly 'don't get it'. Nothing else has changed on my system. I am running the following software: Screen version 3.09.13 (FAU) 5-Sep-02 aterm version 0.4.2 Has anyone else had this problem? Thanks in advance for any help you can give me. I use screen and aterm a lot, so losing the combo really really hurts. Thanks again. -- ________________________________________________________________________ Mike Barrett | "I used to read, now I go to raves." mike@daboyz.org | -- Random MUNI Rider, speaking www.daboyz.org | to my friend Allison. ------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message