From owner-freebsd-ports Sun Jan 10 02:12:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA27753 for freebsd-ports-outgoing; Sun, 10 Jan 1999 02:12:54 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from corp.au.triax.com (slwag1p28.ozemail.com.au [203.108.157.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA27740; Sun, 10 Jan 1999 02:12:49 -0800 (PST) (envelope-from jim@corp.au.triax.com) Received: from localhost (jim@localhost) by corp.au.triax.com (8.9.2/8.9.2) with ESMTP id VAA03461; Sun, 10 Jan 1999 21:12:14 +1100 (EST) Date: Sun, 10 Jan 1999 21:12:13 +1100 (EST) From: Jim Mock To: FreeBSD-gnats-submit@FreeBSD.ORG cc: ports@FreeBSD.ORG Subject: Re: ports/9423: new port: aterm-0.2.0 In-Reply-To: <199901100916.UAA00160@corp.au.triax.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 10 Jan 1999 jim@phrantic.phear.net wrote: > > >Number: 9423 > >Category: ports > >Synopsis: new port: aterm-0.2.0 > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-ports > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: change-request > >Submitter-Id: current-users > >Arrival-Date: Sun Jan 10 01:20:00 PST 1999 > >Closed-Date: > >Last-Modified: > >Originator: Jim Mock > >Release: FreeBSD 2.2.8-RELEASE i386 > >Organization: > Triax Internet Services > >Environment: > > Tested on 2.2.8-RELEASE, 2.2.7-RELEASE, 2.2.2-RELEASE > > >Description: > > For some reason, aterm seems to have a real problem with the bash shell. > However, it works fine with csh and tcsh. I've had 4 people confirm > this. I'm going to contact the people responsible and see if a) they know > about it, b) if it's being fixed for bash users. It's a decent program, > so I figured I'd submit it anyway for the c shell users even with the bash > problems. > [snip..] Don't know if this is relevant or not, but I have more info on what I mentioned above. The problem doesn't happen with bash-1.14.7, only with 2.x from what I can tell. It works fine with csh, tcsh, and bash-1.14.7. -- : Jim Mock | [jim@corp.au.triax.com] : : System Administrator | http://www.triax.com/ : : Triax Internet Services | ----------------------------- : : Portland, OR USA | FreeBSD: The Power to Serve : : Wagga Wagga, NSW Australia | http://www.freebsd.org/ : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message