Thanks Chris.
So the way I read it is that many people didn't like bash 4.1 behaviour
(expansion), but the fact that a $ is replaced with \$ in 4.2 is a bug no one
knows how to fix.
Is this correct?
(I don't want expansion either.)
Regards,
Diggory
On Tuesday 14 January 2014 10:57:03 Chris
On Tuesday 14 January 2014 10:57:46 Chris Down wrote:
> On 2014-01-13 20:42:39 -0500, Chet Ramey wrote:
> > You can set the `direxpand' option and probably get around most of this,
> > with the change that variables will be expanded upon completion, as in
> > bash-4.1.
>
> Er, somehow I missed thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/15/14 5:07 AM, Diggory Hardy wrote:
> Thanks Chris.
>
> So the way I read it is that many people didn't like bash 4.1 behaviour
> (expansion), but the fact that a $ is replaced with \$ in 4.2 is a bug no one
> knows how to fix.
>
> Is this cor
Sorry Chet, for some reason I didn't see your reply until after I'd replied to
Chris.
On Wednesday 15 January 2014 07:50:09 Chet Ramey wrote:
> On 1/15/14 5:07 AM, Diggory Hardy wrote:
> > Thanks Chris.
> >
> > So the way I read it is that many people didn't like bash 4.1 behaviour
> > (expansio
On 1/15/14 12:14 AM, dran...@suddenlinkmail.com wrote:
> Bash Version: 4.2
> Patch Level: 45
> Release Status: release
>
> Description:
> Including the current time in the prompt causes line wrap issues on the
> command line. This is apparently a regression because for at least 4 out of 5
