Lasse Kärkkäinen wrote:
>> Can you reproduce this with bash-4.0 with all 24 patches applied? I
>> still have more testing to do, but I haven't been able to reproduce
>> it on my Mac OS X development machines.
>
> Dunno what was wrong, but redownloading the patches solved the patching
> issue.
>
Ville Skyttä wrote:
> Hello,
>
> Is it intentional that COMP_CWORD may have a negative value within a
> completion function? I did not find any indication of that in the bash man
> page. For example:
>
> foo()
> {
> echo "COMP_CWORD:$COMP_CWORD"
> }
> complete -F f
Henning Bekel wrote:
>> I wonder if we could specify whether or not to completely redraw
>> the line with a return status.
>
> As far as I see it there hasn't been a reason to return a specific
> value from a function bound via -x in the past, has there? Still,
> maybe some users have done so o
Dave B wrote:
On Friday 17 July 2009, Linda Walsh wrote: (majorly abbreviated)
where output 'time' cmd "go"? I.e. Howto pipe_ 'time' output to _prog_ [?]
or file?
Please see http://mywiki.wooledge.org/BashFAQ/032
An excellent and thorough webpage, but it doesn't exactly
answer my ques
A previous note had me wondering why the syntax for using
curly braces to group expressions wasn't able to be the same as
using 'paren's.
I.e. on the same line, why do I need an extra ";" before the '}':
(ls) works
{ls} fails -- needs {ls;}
I know braces can be part of a filename, but they can a
Linda Walsh wrote:
> A previous note had me wondering why the syntax for using
> curly braces to group expressions wasn't able to be the same as
> using 'paren's.
Braces are reserved words. Parentheses are operators. Blame
Steve Bourne.
--
``The lyf so short, the craft so long to lerne.'' - Ch
