Hi,
when using & at the end of a command, bash prints messages like:
[EMAIL PROTECTED]:~$ kwrite &
=>[1] 20986
[EMAIL PROTECTED]:~$
=>[1]+ Donekwrite
[EMAIL PROTECTED]:~$
is there a way to tell bash not to print those lines marked with => ?
I could not find any comma
There seems to be a problem with bash 3.1.10 on FreeBSD as described in
this thread.
---
http://lists.freebsd.org/pipermail/freebsd-stable/2006-March/023123.html
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-b
FYI.
Original Message
Subject: Re: bash 3.1.10 breaks configure scripts (was Re: configure
scripts ignores parameters)
Date: Sun, 5 Mar 2006 04:01:19 -0500
From: Kris Kennaway <[EMAIL PROTECTED]>
To: freebsd-stable@FreeBSD.ORG, [EMAIL PROTECTED], [EMAIL PROTECTED]
Re
Francesco Montorsi wrote:
> Hi,
> when using & at the end of a command, bash prints messages like:
>
> [EMAIL PROTECTED]:~$ kwrite &
> =>[1] 20986
> [EMAIL PROTECTED]:~$
> =>[1]+ Donekwrite
> [EMAIL PROTECTED]:~$
>
> is there a way to tell bash not to print those line
Is it intentional that the following script, which worked in 2.05b now
produces errors in 3.1:
: `: "\\""`
That now results in: unexpected EOF while looking for matching ``'
Using a third backslash fixes it but this is inconsistent with ash bash2
bsh ksh pdksh and zsh.
Oliver
This e-mail and a
Does redirecting to /dev/tty work if the original stdout of the shell was NOT a tty? This script runs as a cron job so it has no tty.
Also is there a better way to save the original stdout and switch back to it
than this:
trap "cat $LOG > &3" ERR
{
foo
bar
} 3>&1 > /dev/null
Chet Ramey w
Markus Laire wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i386
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-pc-linux-gnu'
> -DCONF_VENDOR='pc' -DLOCALEDIR='
Brian Minton wrote:
> 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
Chet Ramey wrote:
> Now that bug-bash appears to have arisen from the ashes, I will send
> out the updated patch 10 again.
These following blog messages about the lists had interesting
information aout the recent problems.
http://www.fsf.org/blogs/sysadmin/lists
https://savannah.gnu.org/foru
Chet Ramey wrote:
Mike Jakubik wrote:
FYI.
This has been a known issue with bison-1.75 for over three years:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=167635;archive=yes
http://lists.gnu.org/archive/html/bug-bash/2003-01/msg00061.html
http://lists.gnu.org/archive/html/bug-bash/
10 matches
Mail list logo
