Re: Document what's allowed in function names

2011-05-24 Thread Chet Ramey
> 2011-04-11, 09:51(-04), Chet Ramey: > >> Machine Type: i686-pc-linux-gnu > >> > >> Bash Version: 4.2 > >> Patch Level: 8 > >> Release Status: release > >> > >> Description: > >>man bash is currently lacking information on what is allowed for > >> function > >>names. It implies name wit

Re: bash trap techniques for group-command in a pipeline

2011-05-24 Thread john.ruckstuhl
Solution... this works nicely: # print opening html echo "" # on error, print msg and exit $STATUS trap myERRhandler ERR myERRhandler () { local STATUS=$? printf "Trouble: trapped ERR, exiting %s\n" $STATUS >& 2 exit $STATUS } # on exit, print

Re: Document what's allowed in function names

2011-05-24 Thread Stephane CHAZELAS
2011-04-11, 09:51(-04), Chet Ramey: >> Machine Type: i686-pc-linux-gnu >> >> Bash Version: 4.2 >> Patch Level: 8 >> Release Status: release >> >> Description: >> man bash is currently lacking information on what is allowed for >> function >> names. It implies name with name () compound

edit-and-execute-command is appropriately named, weird

2011-05-24 Thread David Thomas
Hi all, In using bash over the years, I've been quite happy to be able to hit ctrl-x ctrl-e to pull up an editor when my input has grown too complicated. When using read -e for input, however, the behavior I find makes a lot less sense: the input line is still opened in an editor, but the result