Re: nullglob option breaks complex parameter expansion/deletion

Hi Chet Thanks for your very prompt reply. I understand that globbing is happening, but I don't understand why deleting a parameter should occur with nullglob set if the parameter matches but the word to delete doesn't. The bash behavior seems to make this construct useful only for file name del

Re: nullglob option breaks complex parameter expansion/deletion

> I also noticed in the POSIX standard that quoting the word part should > cause it to be literal and prevent globbing. If I try this in bash, I > get the same result as in my original message, that is: > > $ shopt -s nullglob > $ connectioninfo='${HOST%%".*"} ${USER}' > $ echo $connectioninfo >

Inconsistent handling of arrays.

Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='lin$uname output: Linux crx 2.6.12 #4 Thu Jun 30 12:33:41 EST 2005 i686 unknown unk$Machine Type: i686-pc-linux-g

Re: Controlling terminal race condition

Paul Jarc wrote: > Jeff Miller <[EMAIL PROTECTED]> wrote: > >>It is possible on our test Solaris 8 system that the original >>calling bash shell will set the controlling process of the terminal >>to the pid that it originally forked to after the new process had >>been created. In this case is not

Re: Feature-Request: Append command to history

Matthias Schniedermeyer wrote: > Thank you for this great news. :-) > > How do you plan to "fix" that bug? Don't delete the last command from the history if it was pushed with `history -s'. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet )

Re: nullglob option breaks complex parameter expansion/deletion

Michael Wardle wrote: > Hi Chet > > Thanks for your very prompt reply. > > I understand that globbing is happening, but I don't understand why > deleting a parameter should occur with nullglob set if the parameter > matches but the word to delete doesn't. The bash behavior seems to make > this c

Re: Inconsistent handling of arrays.

Aaron Marks wrote: > Bash Version: 3.0 > Patch Level: 0 > Release Status: release > > Description: > The array handling is inconsistent across global variables and > local variables. See the Repeat-By for more information. This is the same problem, with the same fix, as the `decl

Re: nullglob option breaks complex parameter expansion/deletion

On Sat, 2005-07-02 at 12:24 -0400, Chet Ramey wrote: > Michael Wardle wrote: > > Hi Chet > > > > Thanks for your very prompt reply. > > > > I understand that globbing is happening, but I don't understand why > > deleting a parameter should occur with nullglob set if the parameter > > matches but

Expansions in arithmetic commands and subscripts

Configuration Information [Automatically generated, do not change]: Machine: i586 OS: cygwin Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i586' -DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='i586-pc-cygwin' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/ locale' -DPACKAGE='bash' -

declare -f and for (( ... ))

Configuration Information [Automatically generated, do not change]: Machine: i586 OS: cygwin Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash.exe' -DCONF_HOSTTYPE='i586' -DCONF_OSTYPE='cygwin' -DCONF_MACHTYPE='i586-pc-cygwin' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/ locale' -DPACKAGE='bash' -

(feature request) here-document, but from a file

Dear Chet, It would be nice if I can read a file and process it as though it was here-document text in the script. Mainly, I want variable substitution, without calling lots of 'sed'. In Python, you would do print "..." % ... So, perhaps, you can use syntax like cat <<+ file cat <<<

Re: (feature request) here-document, but from a file

On Sat, 2 Jul 2005, William Park wrote: Dear Chet, It would be nice if I can read a file and process it as though it was here-document text in the script. Mainly, I want variable substitution, without calling lots of 'sed'. In Python, you would do print "..." % ... So, perhaps, you can us

Re: (feature request) here-document, but from a file

Chris F.A. Johnson wrote: > William Park wrote: > >It would be nice if I can read a file and process it as though it was > >here-document text in the script. Mainly, I want variable substitution, > >without calling lots of 'sed'. > > > >In Python, you would do > > print "..." % ... > > > >So, pe

Re: (feature request) here-document, but from a file

William Park <[EMAIL PROTECTED]> wrote: > It would be nice if I can read a file and process it as though it was > here-document text in the script. Mainly, I want variable substitution, > without calling lots of 'sed'. eval "blah

Re: (feature request) here-document, but from a file

On Sat, Jul 02, 2005 at 05:48:40PM -0600, Bob Proulx wrote: > Chris F.A. Johnson wrote: > > William Park wrote: > > >It would be nice if I can read a file and process it as though it was > > >here-document text in the script. Mainly, I want variable substitution, > > >without calling lots of 'sed'

Re: (feature request) here-document, but from a file

Chris F.A. Johnson wrote: > On Sat, 2 Jul 2005, William Park wrote: > >> Dear Chet, >> >> It would be nice if I can read a file and process it as though it was >> here-document text in the script. Mainly, I want variable substitution, >> without calling lots of 'sed'. >> >> In Python, you would d