From owner-freebsd-stable Sun Sep 8 17:47:19 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2649537B400; Sun, 8 Sep 2002 17:47:12 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D1E143E4A; Sun, 8 Sep 2002 17:47:11 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.6/8.12.2) with ESMTP id g890l4fO005294; Sun, 8 Sep 2002 17:47:04 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.6/8.12.5/Submit) id g890l4QI005290; Sun, 8 Sep 2002 17:47:04 -0700 (PDT) Date: Sun, 8 Sep 2002 17:47:04 -0700 From: "David O'Brien" To: Vasil Dimov Cc: freebsd-stable@freebsd.org, freebsd-ports@freebsd.org Subject: Re: bash directory completion annoyingly changes from 2.05a to 2.05b Message-ID: <20020909004704.GA4973@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20020908143027.GA16572@polejan.bl-52.studgrad.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020908143027.GA16572@polejan.bl-52.studgrad.net> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I don't like it either. But AFAIK, the change is not due to any FreeBSD-specific patch in the FreeBSD port. Therefore it is purely a Bash issue and the bash author should be contacted. Or if you track this down, I'd accept a patch for the FreeBSD bash port to return the traditional behavior. -- David On Sun, Sep 08, 2002 at 05:30:27PM +0300, Vasil Dimov wrote: > after upgrading from 2.05a to 2.05b i noticed that directory completions > do not work as before and probably the new way is "wrong". > > being in /usr/local/etc and desiring to run ./rc.d/030.apache.sh it is > usual to type: > /usr/local/etc# ./r03 > but after the first now (in 2.05b) i get > "./rc.d " instead of "./rc.d/" and i have to backspace and manually type > the slash: > /usr/local/etc# ./r/03 > and i find that annoying, isn't it? > can it be changed with `set SOMETHING' or like? > i did not find anything about it. > ----- > From: "Patrick O'Reilly" : > > Experimenting, I found this: > /usr/local/etc# rc. ==> rc.d/ > /usr/local/etc# sh r ==> sh rc.d/ > /usr/local/etc# . r ==> . rc.d/ > > So, it seems to me that when bash auto-completes the first token on the > line, it will omit the trailing / on directory names, but when it > autocompletes an argument (2nd or later token on the line) it includes the > trailing /. > > These are my observations - I don't know whether this should be considered > RIGHT or WRONG? Admittedly - I cannot think of any reason why one would > want to use a directory name as the first token on a line, so the > behaviour does seems strange. > ----- > From: Phil Kernick > > It's already been reported to the bash developers, and there is a patch. > > Refer to: http://www.geocrawler.com/mail/msg.php3?msg_id=9514404&list=342 > > What this probably means is that 2.05b should not be included in the ports > collection that makes it into 4.7-RELEASE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message