Patterns of dynamic scoping and nested routines.

2011-02-21 Thread Steven W. Orr
It has been an exciting weekend for me. I studied the dynamic vs static scoping rules and I think I have a better handle on things, but I have a few questions. It seems that there's no reason why we are not allowed to write nested functions. Nested functions would not be visible to other functi

Re: ``complete -b'' does not include ``coproc''

2011-02-21 Thread Clark J. Wang
On Mon, Feb 21, 2011 at 10:26 PM, Chet Ramey wrote: > On 2/21/11 3:55 AM, Clark J. Wang wrote: > > > And even ``helptopic'' does not show ``coproc'' either: > > > > # compgen -A helptopic co > > command > > compgen > > complete > > compopt > > continue > > # > > > > Should ``coproc'' be included

Re: ``complete -b'' does not include ``coproc''

2011-02-21 Thread Chet Ramey
On 2/21/11 3:55 AM, Clark J. Wang wrote: > And even ``helptopic'' does not show ``coproc'' either: > > # compgen -A helptopic co > command > compgen > complete > compopt > continue > # > > Should ``coproc'' be included in ``-A helptopic''? At this point, helptopic is a synonym for builtin. --

Re: ``complete -b'' does not include ``coproc''

2011-02-21 Thread Chet Ramey
On 2/21/11 3:55 AM, Clark J. Wang wrote: > On Mon, Feb 21, 2011 at 4:21 PM, Pierre Gaston wrote: > >> >> >> On Mon, Feb 21, 2011 at 10:12 AM, Clark J. Wang wrote: >> >>> Tested with 4.2: >>> >>> bash-4.2# complete -b help >>> bash-4.2# help co >>> command compgen complete compopt continue >

Re: Do more testing before a release?

2011-02-21 Thread Marc Herbert
Le 17/02/2011 15:46, Eric Blake a écrit : > On 02/16/2011 09:51 PM, Clark J. Wang wrote: >> I know little about open source development process (and control?). I just >> don't know where to get the bash code (like CVS, SVN respository) before >> it's released. I think it's better to make it open to

Re: ``complete -b'' does not include ``coproc''

2011-02-21 Thread Clark J. Wang
On Mon, Feb 21, 2011 at 4:21 PM, Pierre Gaston wrote: > > > On Mon, Feb 21, 2011 at 10:12 AM, Clark J. Wang wrote: > >> Tested with 4.2: >> >> bash-4.2# complete -b help >> bash-4.2# help co >> command compgen complete compopt continue >> bash-4.2# >> >> -- >> Clark J. Wang >> > It's probab

Solved: Re: how to workaroun 'nl' being added to input-line after 49 characters....

2011-02-21 Thread Linda Walsh
BTW, thanks much for an overlooked, and elegant solution! Bob Proulx wrote: Linda Walsh wrote: there some easy way to tell bash either to not keep track of what it thinks is the screen width (and just allow it to wrap, if that's possible), or to reset bash's idea of where it thinks it is on t

no way to give 'select' a default value

2011-02-21 Thread jidanni
There is no way to give the 'select' command a default value, so all the user does is need to hit return. $ help select ... If the line is empty, WORDS and the prompt are redisplayed. Well OK, If EOF is read... but many users aren't familiar with ^D.

Re: ``complete -b'' does not include ``coproc''

2011-02-21 Thread Pierre Gaston
On Mon, Feb 21, 2011 at 10:12 AM, Clark J. Wang wrote: > Tested with 4.2: > > bash-4.2# complete -b help > bash-4.2# help co > command compgen complete compopt continue > bash-4.2# > > -- > Clark J. Wang > It's probably because: $ type coproc coproc is a shell keyword likewise help tim do

``complete -b'' does not include ``coproc''

2011-02-21 Thread Clark J. Wang
Tested with 4.2: bash-4.2# complete -b help bash-4.2# help co command compgen complete compopt continue bash-4.2# -- Clark J. Wang