4.0 patch 25 breaks with gcc 3.3

Bash-4.0 official patch 25 adds a section that looks to the compiler like a nested C comment. Obviously somebody recognized this and added #if 0 ... #endif around the whole comment. Alas, GCC 3.3 still errors out: cc -c -DHAVE_CONFIG_H -DSHELL -I/usr/local/include -I. -I../.. -I../.. -I../../in

Bug in the Bash Reference Manual

In section "6.3.2 Is this Shell Interactive?", the Bash Manual advocates: if [ -z "$PS1" ]; then echo This shell is not interactive fi however, this does not work in any shell I've tested (RedHat 4 & 5, OpenSUSE 11.1, SLES 10 & 11). It seems that the idea of testing the prompt variable was

Re: Non-filename completions containing slashes and -o filenames

> I'm trying to figure out how to do the right thing with non-filename > completions containing slashes in a function that was passed to complete > along > with -o filenames. > > For example: > > _foo() > { > COMPREPLY=( $( compgen -W 'a/b c/d e/f/g' -- ${COMP_WORDS[COMP_CWORD]} ) ) > } > co

Re: Porting GNU Projects - BASH

Hello Mark Can you please tell me if this library is independently portable to a new architecture? Also how difficult is it to port it? Also it will be needed to integrate it in the existing library headers? Any points on that? Thanks bornlibra23 -- View this message in context: http://www.nabbl

Re: Porting GNU Projects - BASH

Thanks Mark Can you tell me does the ICU library have the mbrtowc, mbrtomb & like functions? Thanks bornlibra23 -- View this message in context: http://www.nabble.com/Porting-GNU-Projects---BASH-tp24721339p24735376.html Sent from the Gnu - Bash mailing list archive at Nabble.com.