On Jan 5, 12:18 pm, Eric Blake wrote:
> On 01/05/2011 09:57 AM, Greg Wooledge wrote:
>
>
>
> > On Wed, Jan 05, 2011 at 08:21:18AM -0800, chengiz wrote:
> >> So if I get this right, the only time this is a problem is when the
> >> command substitution run
On Jan 1, 11:20 pm, Chet Ramey wrote:
> On 12/31/10 11:01 PM, Sven Mascheck wrote:
>
> > On Fri, Dec 31, 2010 at 12:20:38PM -0800, chengiz wrote:
> >> On Dec 31, 12:20 pm, Sven Mascheck wrote:
>
> >>> (see alsohttp://lists.gnu.org/archive/html/bug-bash/2008-01
On Dec 31, 11:57 am, Eric Blake wrote:
> On 12/31/2010 09:49 AM, Chris F.A. Johnson wrote:
>
> > Fri, 31 Dec 2010 11:49:26 -0500 (EST) linux system
> >>> with default installation settings.
>
> >>> In an earlier version of bash (3.2), the following works
> >>> ls `pwd`/ (expands pwd).
>
> >>> In b
On Dec 31, 12:20 pm, Sven Mascheck wrote:
> On Dec 30, 12:59 pm, chengiz wrote:
>
> > > In an earlier version of bash (3.2), the following works
> > > ls `pwd`/ (expands pwd).
>
> > > In bash 4.1 it does not. Am I missing a setting or something?
> > >
On Dec 30, 12:59 pm, chengiz wrote:
> Command substitution and auto completion are not working well together
> in the latest version of bash (4.1). This was on an x64 linux system
> with default installation settings.
>
> In an earlier version of bash (3.2), the following
Command substitution and auto completion are not working well together
in the latest version of bash (4.1). This was on an x64 linux system
with default installation settings.
In an earlier version of bash (3.2), the following works
ls `pwd`/ (expands pwd).
In bash 4.1 it does not. Am I missing a
