bash dies when trying to write to a tcp socket that has been closed on the other end

2007-06-06 Thread Ralf Goertz
Configuration Information [Automatically generated, do not change]: Machine: i586 OS: linux-gnu Compiler: gcc -I/usr/src/packages/BUILD/bash-3.2 -L/usr/src/packages/BUILD/bash-3.2/../readline-5.2 Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586' -DCONF_OSTYPE='linux-gnu'

typeset does not make variable local in function

2007-06-06 Thread Clay Harris
Problem: typeset, when used in a function should always mark the variable as local. When bash is in ksh mode, it fails to do this. Previous versions did not have this problem, e.g. GNU bash, version 3.00.15(1)-release (i386-redhat-linux-gnu) Recent versions of ksh seem to be exhibiting the same

Bash command completion when not connected to a terminal

2007-06-06 Thread raner
Hi all, I am trying to integrate bash with a Java application, i.e. bash is started as a process and the Java application sends data to the process's stdin and reads data from stdout/stderr. This works reasonably well, but I am having a problem with completion, e.g. the user pressing TAB to

Re: Bash command completion when not connected to a terminal

2007-06-06 Thread Paul Jarc
raner [EMAIL PROTECTED] wrote: The completion seems to work, but I do not receive the completed filename from the shell's stdout. It's written to stderr, not stdout. paul ___ Bug-bash mailing list Bug-bash@gnu.org

Re: Bash command completion when not connected to a terminal

2007-06-06 Thread raner
Paul Jarc wrote: raner [EMAIL PROTECTED] wrote: The completion seems to work, but I do not receive the completed filename from the shell's stdout. It's written to stderr, not stdout. Thanks for your reply, Paul. I'm reading stderr, too, and it doesn't show up there either. I am

Re: typeset does not make variable local in function

2007-06-06 Thread Chet Ramey
Clay Harris wrote: Problem: typeset, when used in a function should always mark the variable as local. When bash is in ksh mode, it fails to do this. I can't reproduce this with bash-3.0, bash-3.1, or bash-3.2 (all patched) on MacOS X and FC6. Bash does not have a `ksh mode'. Chet --