Re: redirecting output of lynx --dump
From: John L (jl_at_lammtarra.notthisbit.fslife.co.uk)
Date: 12/23/04
- Next message: Dan Mercer: "Re: pdksh: question about "read pipline bug""
- Previous message: joe_at_invalid.address: "Re: yesterday date"
- In reply to: Nikolaus Wagner: "Re: redirecting output of lynx --dump"
- Next in thread: Bill Marcum: "Re: redirecting output of lynx --dump"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 23 Dec 2004 15:13:52 -0000
"Nikolaus Wagner" <spanferkel.10.frissdichtot@spamgourmet.com> wrote in message
news:pan.2004.12.23.13.52.19.429015@spamgourmet.com...
> Am Thu, 23 Dec 2004 10:58:28 +0000 schrieb John L:
>
> >
> > "nabis" <nabis@nomail.net> wrote in message news:41CA75E7.90007@nomail.net...
> >> Hi group!
> >>
> >> Need a little help on redirecting the output of two or more lynx --dump
> >> commands
>
> > You can use round brackets (parentheses) to execute lynx
> > in a subshell, or curly brackets (braces) to run them as
> > a list -- in this case you need an extra semi-colon after
> > the last command.
> >
> > ( lynx --dump $URL1 ; lynx --dump $URL2 ) | sed ... | sort
> > { lynx --dump $URL1 ; lynx --dump $URL2 ; } | sed ... | sort
> {echo "Hallo";echo "Hi";} | sort
> bash: ${echo "Hallo";echo "Hi";}: bad substitution
>
> With parantheses it works.
That -- with the $ sign -- is something else entirely.
( command ) -- subshell
{ command; } -- list of commands (only one shown here)
$( command ) -- command substitution
${ not command } -- parameter expansion
See manual for more details.
-- John.
- Next message: Dan Mercer: "Re: pdksh: question about "read pipline bug""
- Previous message: joe_at_invalid.address: "Re: yesterday date"
- In reply to: Nikolaus Wagner: "Re: redirecting output of lynx --dump"
- Next in thread: Bill Marcum: "Re: redirecting output of lynx --dump"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|