Quoting Chet Ramey <[EMAIL PROTECTED]>:
> > On Tue, 3 Apr 2007, Chet Ramey wrote:
> >
> > It is an interesting position for POSIX to take, given that in general
> > Unix is silent on success.
>
> It's the logical thing to do, considering the potential ambiguity that
> exists when you use a directo
Eric Blake wrote:
According to Matthew Woehlke on 4/2/2007 5:09 PM:
If nothing else, I'll stand by it being a bash bug, if only in the docs
because they are not sufficiently clear. :-)
The POSIX rules here are [snip]
Ok, but the man page is still unclear. :-)
(Sigh. Curse Solaris and their
> On Tue, 3 Apr 2007, Chet Ramey wrote:
>
> > > [...] and there appear to
> > > be no options at all to turn this superfluous output off.
> >
> > This is, as Eric Blake noted, required POSIX behavior. As to the manual:
>
> It is an interesting position for POSIX to take, given that in g
On Tue, 3 Apr 2007, Chet Ramey wrote:
> > [...] and there appear to
> > be no options at all to turn this superfluous output off.
>
> This is, as Eric Blake noted, required POSIX behavior. As to the manual:
It is an interesting position for POSIX to take, given that in general
Unix is s
> Bash Version: 3.2
> Patch Level: 15
> Release Status: release
>
> It seems like this extra output only occurs when CDPATH is used for the
> cd operation. Also, popd and pushd also have similarly inconvenient
> outputs. None of this is documented in the manual, and there appear to
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Tony Balinski on 4/2/2007 9:01 AM:
> It seems like this extra output only occurs when CDPATH is used for the
> cd operation. Also, popd and pushd also have similarly inconvenient
> outputs. None of this is documented in the man
