Date: Fri, 5 Jan 2001 20:48:26 -0700 From: Bill Currie To: djgpp AT delorie DOT com Subject: Re: bash 2.04 Message-ID: <20010105204825.A21718@taniwha.org> Mail-Followup-To: djgpp AT delorie DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from 386sx@my-deja.com on Sat, Jan 06, 2001 at 01:42:25AM +0000 Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sat, Jan 06, 2001 at 01:42:25AM +0000, 386sx wrote: > My bash 2.04 won't recognize .sh files as executable from the command line > unless I append the ".sh". > i.e. "rundos" won't work, but "rundos.sh" works. Is there some > variable I need to set or unset? Yeah, the OLD_HABITS var needs to be audited. Unix does not do default extentions like DOS does. Yes, djgpp bash handles .com, .exe and .bat, but only because those are nomally the only executable programs in DOS and having to change that habit as well would have caused a revolt. HINT: in bash, the tab key is your friend. I don't know about in djgpp, but in unix, bash will complete both partial commands and args. eg: xc foo will (assuming xcopy is the only command in the path starting with xc and there's foobar in the current directory) expand to xcopy foobar If there's an ambiguity, bash will beep at you. You can then press tab again and get a list of matches. Another thing to remember: . (the current directory) is, unlike command.com NOT (by default) in the path (this caused me no end of grief until I got used to it). Bill -- Leave others their otherness. -- Aratak