sorry if this mail arrives twice, but the first mail didn't seem to
made it through.
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: openbsd4.4
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
-DCONF_OSTYPE='openbsd4.4' -DCONF_MACHTYP
Tim Hatch wrote:
> Pilot:~/tmp/bash-4.0 tim$ coproc NAME ls
> [1] 18474
> Pilot:~/tmp/bash-4.0 tim$ ./bash: line 32: NAME: command not found
>
> [1]+ Exit 127coproc COPROC NAME ls
For some reason it expects a compound command on named coprocesses,
http://bash-ha
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: darwin9.6.0
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -
DCONF_OSTYPE='darwin9.6.0' -DCONF_MACHTYPE='i386-apple-darwin9.6.0' -
DCONF_VENDOR='apple' -DLOCALEDIR='/usr/local/share/
Configuration Information [Automatically generated, do not change]:
Machine: hppa2.0
OS: hpux10.20
Compiler: /net/appl/gcc-3.3/bin/gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='hppa2.0'
-DCONF_OSTYPE='hpux10.20' -DCONF_MACHTYPE='hppa2.0-hp-hpux10.20'
-DCONF_VENDOR='hp' -DLOCALEDIR='/
Configuration Information
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/locale'
-DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H
siglist.c must #include "bashintl.h" -- bash 4.0 fails to build for me
on HP-UX 10.20 with gcc, with "unresolved symbol _" at final link time
until I add that #include.
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
From: bot...@gmail.com
To: bug-bash@gnu.org
Subject: Make error
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: cygwin
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='i686-pc-cygwin'
-DCONF
On Tuesday 24 February 2009 21:14:46 Vincent Lefevre wrote:
> On 2009-02-24 19:32:05 -0500, Paul Jarc wrote:
> > Vincent Lefevre wrote:
> > > I get the following errors with bash 3.2.39 under Debian/unstable:
> > >
> > > bash -c 'alias a="echo OK >&2"
> > > a
> > >
> > > > /dev/null a'
> > >
> >
On 2009-02-24 19:32:05 -0500, Paul Jarc wrote:
> Vincent Lefevre wrote:
> > I get the following errors with bash 3.2.39 under Debian/unstable:
> >
> > bash -c 'alias a="echo OK >&2"
> > a
> > > /dev/null a'
> > bash: line 1: a: command not found
> > bash: line 2: a: command not found
>
> aliase
Vincent Lefevre wrote:
> I get the following errors with bash 3.2.39 under Debian/unstable:
>
> bash -c 'alias a="echo OK >&2"
> a
> > /dev/null a'
> bash: line 1: a: command not found
> bash: line 2: a: command not found
aliases aren't expanded by a non-interactive bash by default. If you
do
I get the following errors with bash 3.2.39 under Debian/unstable:
bash -c 'alias a="echo OK >&2"
a
> /dev/null a'
bash: line 1: a: command not found
bash: line 2: a: command not found
$ bash --posix
bash-3.2$ alias a="echo OK >&2"
bash-3.2$ a
OK
bash-3.2$ > /dev/null a
bash: a: command not fou
Chet Ramey wrote:
>
> I posted a patch for this earlier. Look at
>
> http://lists.gnu.org/archive/html/bug-bash/2009-02/msg00153.html
>
> and see if it fixes things for you.
>
> Chet
>
Ah yes, that was indeed the problem. Fixed for me as well now. Thanks.
--
View this message in context:
Chet Ramey schrieb:
Bernd Eggink wrote:
I'm still having problems with the cd builtin. In bash 3, the commands
cd
cd ""
both changed to the user's home directory. In bash 4 (with patch
"save-current-token" applied)
cd ""
does nothing. Bug or feature?
I get the same behavior from b
Richard Leeden wrote:
> Unfortunately doesn't work for me
>
> I'm doing something to Bernd - i.e. I have a function called cd that calls
> the builtin cd after doing some extra things. In bash 4.0 with my cd
> function enabled I get a bus error and the shell quits each time I attempt a
> tab
Bernd Eggink wrote:
> I'm still having problems with the cd builtin. In bash 3, the commands
>
>cd
>cd ""
>
> both changed to the user's home directory. In bash 4 (with patch
> "save-current-token" applied)
>
>cd ""
>
> does nothing. Bug or feature?
I get the same behavior from bas
monoped wrote:
>
> Works for me, too. Thanks!
>
Unfortunately doesn't work for me
I'm doing something to Bernd - i.e. I have a function called cd that calls
the builtin cd after doing some extra things. In bash 4.0 with my cd
function enabled I get a bus error and the shell quits each tim
I'm still having problems with the cd builtin. In bash 3, the commands
cd
cd ""
both changed to the user's home directory. In bash 4 (with patch
"save-current-token" applied)
cd ""
does nothing. Bug or feature?
Regards,
Bernd
--
Bernd Eggink
http://sudrala.de
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu'
-DCONF_VENDOR='unknown'
-DLOCALEDIR='/home/arvid/local/
Chet Ramey schrieb:
Bernd Eggink wrote:
I normally wrap the builtin cd into a function cd, which does some
additional things and then calls the builtin. Example:
function cd
{
local list=$(echo *.bui)
# ...
builtin cd "$1"
}
I have a PS1 like this:
PS1="\\w \$ "
W
20 matches
Mail list logo