Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
On Tue, Jun 10, 2008 at 11:20:54AM +0200, Andreas Schwab wrote:
> [EMAIL PROTECTED] writes:
>
> > SUSv3> Some older implementations searched the current directory
> > SUSv3> for the file, even if the value of PATH disallowed it. This
> > SUSv3> behavior was omitted from this volume of IEEE Std
> >
[EMAIL PROTECTED] writes:
> SUSv3> Some older implementations searched the current directory
> SUSv3> for the file, even if the value of PATH disallowed it. This
> SUSv3> behavior was omitted from this volume of IEEE Std
> SUSv3> 1003.1-2001 due to concerns about introducing the
> SUSv3> susceptib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Andreas Schwab on 6/10/2008 3:20 AM:
| [EMAIL PROTECTED] writes:
|
|> SUSv3> Some older implementations searched the current directory
|> SUSv3> for the file, even if the value of PATH disallowed it.
Yes, bash has a bug here, to the poin
On Tue, Jun 10, 2008 at 06:21:13AM -0600, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to Andreas Schwab on 6/10/2008 3:20 AM:
> | [EMAIL PROTECTED] writes:
> |
> |> SUSv3> Some older implementations searched the current directory
> |> SUSv3> for the file, even
Stephane Chazelas wrote:
So it is indeed a bug.
Yes, it is. I fixed it the last time this came up, in January.
So the fix should just be to change the 1 to 0 above.
It's not quite, but the right fix is very similar: setting it to 0
when posix mode is enabled.
Chet
--
``The lyf so short,
On Tue, Jun 10, 2008 at 11:19:47AM -0400, Chet Ramey wrote:
[...]
>> So it is indeed a bug.
>
> Yes, it is. I fixed it the last time this came up, in January.
[...]
Thanks,
It still seems to be there in 3.2.39 which seems to be the
latest version or ftp.gnu.org.
If there's a newer version, wher
Hello,
I have the following lines on my login script, intended to make my history big
enough for me, and not to waste space by keeping several copies of the same
command again anda again:
HISTCONTROL='ignoreboth:erasedups'
HISTSIZE=4096
HISTFILESIZE=4096
To make sure it is working as that, I do
I am trying to create a script that will run continuously until the out of a
command reaches a specific point.
I have a command called showOutput and all it does it output the progress of
running job, i want to create a script or a command that will process this
output and do something else once i