Re: Problem with overridden functions and BASH_SOURCE Array

On 12/14/11 4:13 AM, dethrophes@modt005 wrote: > Bash Version: 4.2 > Patch Level: 8 > Release Status: release > > Description: > Problem with overridden functions having wrong source file name in > BASH_SOURCE Array > see example in Repeat-By section This is an interesting problem.

Re: [Help-bash] How to keep only files match the prefix when do command completion?

Hi Greg, > New users do not mess with programmable completion. Given the context, I though that it was clear that "new users" means users new to command completion. If it was not clear, I make it explicit here. -- Regards, Peng

Re: Print non-readonly variables with declare +r -p

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/14/11 4:10 PM, Dan Douglas wrote: > Ah. I had assumed the single quotes added around array compound asssignment > broke this (intentionally?), but now I see it's valid. I expected declare -a > y='([0]="a" [1]="b c" [2]="d")' to set the first e

Re: Ill positioned 'until' keyword

Bob Proulx writes: > Peng Yu wrote: >> I looks a little wired why 'until' is the way it is now. >> ... >> until test-commands; do consequent-commands; done >> while ! test-commands; do consequent-commands; done > > In the original Bourne shell there is no '!' operator. The 'until' > was a way to