Linda Walsh wrote:
The curly brackets are suposed to be optional.
They are line 2 of the Compound commands list below...
Don't ask me why, but it works when you don't use the function
keyword, but () instead:
foo() [[ 1 ]]
Might be a parsing bug, though you shouldn't use function at all.
On Sun, Jul 18, 2010 at 11:53:02AM -0700, Linda Walsh wrote:
from man bash, to define a function use;
function name compound-command
OR
name () compound-command
right?
And Compound Commands are:
( list)
{ list; )
(( expression ))
[[ expression ]]
...et al
so why
Am 19.07.2010 08:30, schrieb Ken Irving:
On Sun, Jul 18, 2010 at 11:53:02AM -0700, Linda Walsh wrote:
from man bash, to define a function use;
function namecompound-command
OR
name ()compound-command
right?
And Compound Commands are:
(list)
{list; )
(( expression ))
[[
Bernd Eggink mono...@sudrala.de writes:
If the function reserved word is supplied, the parentheses are
optional.
While the grammer has the right rules for this the handling inside of
special_case_tokens isn't right up to it, it only recognizes '{'
following 'function WORD'.
Andreas.
--
On Sun, Jul 18, 2010 at 05:01:05PM -0700, John Reiser wrote:
Lastly since ^J is a newline you can generate one with echo \n.
What does work is either of these:
$ echo ''
$ echo -e -n '\n'
Or printf '\n'.
Or if he wants to use it in a command string, rather than producing it
on a stream,
On Mon, Jul 19, 2010 at 10:46:30AM +0200, Bernd Eggink wrote:
Am 19.07.2010 08:30, schrieb Ken Irving:
On Sun, Jul 18, 2010 at 11:53:02AM -0700, Linda Walsh wrote:
from man bash, to define a function use;
function namecompound-command
OR
name ()compound-command
right?
And
