From owner-freebsd-questions@FreeBSD.ORG Wed Apr 11 23:42:01 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0A4D116A400 for ; Wed, 11 Apr 2007 23:42:01 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from betty.computinginnovations.com (dsl081-227-250.chi1.dsl.speakeasy.net [64.81.227.250]) by mx1.freebsd.org (Postfix) with ESMTP id 9F57213C448 for ; Wed, 11 Apr 2007 23:41:58 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from p28.computinginnovations.com (dhcp-10-20-30-100.computinginnovations.com [10.20.30.100]) (authenticated bits=0) by betty.computinginnovations.com (8.13.8/8.12.11) with ESMTP id l3BNfCaN009834; Wed, 11 Apr 2007 18:41:13 -0500 (CDT) Message-Id: <6.0.0.22.2.20070411183857.0254beb8@mail.computinginnovations.com> X-Sender: derek@mail.computinginnovations.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Wed, 11 Apr 2007 18:40:41 -0500 To: Chad Perrin , FreeBSD Questions From: Derek Ragona In-Reply-To: <20070411224252.GA60179@demeter.hydra> References: <20070411224252.GA60179@demeter.hydra> Mime-Version: 1.0 X-ComputingInnovations-MailScanner-Information: Please contact the ISP for more information X-ComputingInnovations-MailScanner: Found to be clean X-ComputingInnovations-MailScanner-From: derek@computinginnovations.com X-Spam-Status: No Content-Type: text/plain; charset="us-ascii"; format=flowed X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: default shell behavior with aterm X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Apr 2007 23:42:01 -0000 At 05:42 PM 4/11/2007, Chad Perrin wrote: >I've had to solve a problem with unexpected shell behavior when using >aterm (my favorite terminal emulator) a couple of times now. This seems >to be limited to aterm -- the same problems do not arise at the TTY >console or in xterm. > >Back when I first set up the workstation I'm currently using, with >FreeBSD 6.1, one of the unexpected differences from what's familiar to >me (having come from Debian GNU/Linux) was the fact that in aterm the >open parenthesis character, "(", would behave as a backspace. I solved >the problem at the time, with a bit of searching around. Part of what I >did to solve the problem involved entering the following command into >the .bashrc file for my user account: > > stty erase2 '^?' > >Since then, something happened (I just wasn't careful enough with my >edits that file, I guess) to that line. Last night, I found myself >trying to remember how to solve the problem of REPLs like OCaml's >toplevel and the interactive UCBLogo shell treating the open parenthesis >character as a backspace. > >Another part of the solution the first time around -- and one that has >not gone away and needed to be refixed -- is to comment out these lines >in the file /usr/ports/x11/aterm/Makefile: > > .if !defined(WITH_BSDEL) > CONFIGURE_ARGS+= --disable-backspace-key --disable-delete-key > .endif > >My question is this: > >Is there some (good) reason that aterm's Makefile contains these lines? >Is there some logically justified reason for causing aterm to break the >principle of least surprise in this fashion -- since it obviously works >differently (surprise!) from the behavior of other means of using the >shell? > >Is this a bug I should submit? Actually you might want to have an entry added for this terminal to terminfo and termcap databases. I don't see an entry for it, and suspect it is using one of the generic definitions. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support.