> On Fri, Dec 9, 2011 at 11:24, Chet Ramey wrote:
> > > Bash-4.2.20 does not have `direxpand'. Did I misunderstand you?
> >
> > Yes.
> >
>
> I need to learn English much harder. :)
It can be an especially confusing language. :-)
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
On Fri, Dec 9, 2011 at 11:24, Chet Ramey wrote:
> On 12/8/11 9:14 PM, Clark J. Wang wrote:
>
> > http://lists.gnu.org/archive/html/bug-bash/2011-09/msg7.html
> > contains a basic summary and includes a patch that adds a `direxpand'
> > shell option to restore the 4.1 behavior.
> >
On 12/8/11 9:14 PM, Clark J. Wang wrote:
> http://lists.gnu.org/archive/html/bug-bash/2011-09/msg7.html
> contains a basic summary and includes a patch that adds a `direxpand'
> shell option to restore the 4.1 behavior.
>
> You can download a version of bash-4.2.20 with this p
On Thu, Dec 8, 2011 at 23:58, Chet Ramey wrote:
> On 12/7/11 9:43 PM, Miles Bader wrote:
> > I notice that recently the behavior of bash completion w/r/t
> > environment variables has changed, in a realy annoying way:
>
> This has enjoyed detailed discussion in the past, on several occasions.
On 12/7/11 9:43 PM, Miles Bader wrote:
> I notice that recently the behavior of bash completion w/r/t
> environment variables has changed, in a realy annoying way:
This has enjoyed detailed discussion in the past, on several occasions.
http://lists.gnu.org/archive/html/bug-bash/2011-09/msg000
On Wed, Dec 7, 2011 at 9:43 PM, Miles Bader wrote:
> I notice that recently the behavior of bash completion w/r/t
> environment variables has changed, in a realy annoying way:
>
> If one has an environment variable like:
>
> ls=/usr/local/src
>
> and then hit to complete the following comma
I notice that recently the behavior of bash completion w/r/t
environment variables has changed, in a realy annoying way:
If one has an environment variable like:
ls=/usr/local/src
and then hit to complete the following command line:
$ cd $ls/ema
where the intent is to do "cd /usr/lo
