On 1/10/21 6:00 PM, bug-bash-requ...@gnu.org wrote:
Message: 3
Date: Sun, 10 Jan 2021 16:49:50 +0100
From: Ángel
To: bug-bash@gnu.org
Subject: Re: non-executable files in $PATH cause errors
Message-ID:
<94646752576f053515ac2ba4656fe0c895f348ce.ca...@16bits.net>
Content-Type: text/plain
bug-bash-requ...@gnu.org wrote:
>Send bug-bash mailing list submissions to
> bug-bash@gnu.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.gnu.org/mailman/listinfo/bug-bash
>or, via email, send a message with subject or body 'help' to
> bug-bash-
[EMAIL PROTECTED] wrote:
---
Message: 1
Date: Tue, 10 Oct 2006 16:08:05 -0500
From: mwoehlke <[EMAIL PROTECTED]>
Subject: How to detect bash?
To: bug-bash@gnu.org
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Anyone have any clever, VERY reliab
erun it with just a very few key-presses.
--
-------
Thomas Mellman Tel: +49/8233/389-037
Creative Telcom Solutions
[EMAIL PROTECTED] Fax: +49/1212-5-115-48-103
___
Bug
Before there was programmable completion, there was simply filename
completion. Now we have smart completion, which you can turn off with
"complete -r". But that doesn't revert to simple filename completion.
It still insists on doing "command completion". That means that if it
thinks that a com
