On Thu, Oct 22, 2009 at 12:15 AM, Jo King wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
> -
On Thursday 22 October 2009 01:10:33 Jan Schampera wrote:
> Jo King schrieb:
> > Fix:
> > [ bash/the read code could
> > detect there's no stdin and sleep for 1-2 seconds]
>
> If you consider this as a bug, the bug is not in Bash (but in the
> application).
>
> In short you request that read
Jo King schrieb:
> Fix:
> [ bash/the read code could
> detect there's no stdin and sleep for 1-2 seconds]
If you consider this as a bug, the bug is not in Bash (but in the
application).
In short you request that read should wait a second, once it got a
end-of-file signalled, I don't think
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/local/share/locale' -DPACKA
Tobias Poschwatta wrote:
> In the following test case test1.sh, bash 4 behaves differently from
> bash 3.1. The behaviour of bash 3.1 is what I would expect to be
> correct. Is this a bug in bash 4 or an intentional change?
>
> Using bash 4:
>
> $ /bin/bash --version
> GNU bash, version 4.0.28(1
Bob Proulx a écrit :
> Todd Partridge wrote:
> If the target has an appended '/' then the destination must be a directory.
But with cp (GNU coreutils) 6.12, appending '/' to the target does not seem
to make any difference?
>> I think the proper behavior here for 'cp -R test2 test' would be to
On Tue, Oct 20, 2009 at 12:59 AM, Bob Proulx wrote:
> Todd Partridge wrote:
>> The cp command will copy to a subdirectory without an appending /
>
> You have reached bug-bash, not bug-coreutils. The 'cp' program is in
> the GNU Coreutils project and so bug reports for 'cp' should go to
> bug-core
On Wed, Oct 21, 2009 at 10:19:52AM +0100, Marc Herbert wrote:
> Tobias Poschwatta a écrit :
> > In the following test case test1.sh, bash 4 behaves differently from
> > bash 3.1. The behaviour of bash 3.1 is what I would expect to be
> > correct. Is this a bug in bash 4 or an intentional change?
On 4 říj, 20:04, Chet Ramey wrote:
> Yarda wrote:
> > With bash-4.0 the mailcheck behaviour is annoying when there is a pseudo
> > message in a mailbox, e.g.:
>
> It's unfortunate that the system's implementors chose a metadata format
> that is indistinguishable from a valid mail message. Since b
Tobias Poschwatta a écrit :
> In the following test case test1.sh, bash 4 behaves differently from
> bash 3.1. The behaviour of bash 3.1 is what I would expect to be
> correct. Is this a bug in bash 4 or an intentional change?
Isn't this related to this change?
http://thread.gmane.org/gmane.comp.
10 matches
Mail list logo