Re: pipe multiple pages in lynx

Chris F.A. Johnson wrote:

> On 2006-01-08, matt_left_coast wrote:
>> Chris F.A. Johnson wrote:
>>
>>> for l in a b c d e f g h i
>>> do
>>> w=http://www/stocks/$l.htm
>>> lynx -dump "$w" && printf "%s complete\n" >&2 ||
>>> printf "%s failed\n" "$w" >&2
>>> done > out.file
>>
>> Now where did the option as to where to dump the lynx error go? Gee, you
>> do like to ignore what is inconvenient don't you?
>
> In exactly the same place as in the other examples. It wasn't in
> any of those, but can be added to any of them.
>
>> Gee, you do like to ignore what is inconvenient don't you?
>
> Nothing was ignored.

Bull***. You simply can't face the fact that your script would become a
redirection nightmare if you add a requirement to redirect an error

>
>> "to the screen and the lynx error messages to either /dev/null/ or to a
>> file to check later"
>
> If you want it, do it. It's the same in all the examples, even
> yours.

Why the *** should I fix YOUR shitty script? Evidently your "cleaner"
script isn't all that FLEXIBLE.

>
>> But I see you are quick to abandon your method as soon as scalability is
>> involved.
>
> The first method was appropriate to a small number of files; since
> the possibility of larger numbers was raised, of course I adjusted
> the code.
>
>

But still have a redirection NIGHTMARE! Your code is UNMANAGEABLE! It can't
even handle the addition of sending custom comments to standard out AND
sending error messages to a separate file!

--


.