Progress info from wget or curl?

[Mike Bonner]

You might try launching the shell in the background.. if it returns
immediately when you do that, I am not where I can try.  If that's the
case, for the -O option, rather than going to /dev/null, point it to a file
in tmp, and do a periodic check of that file. (I think this will work, but
again, I can't try it)
I really wish that open process (on mac) would let you work with shell
commands rather than as just a glorified launcher.  On linux, not sure if
you can do the interactive thing or not with open process.  (another thing
to try)  IF you can with open process, still not sure it will do what you
want. IIRC wget does some funky terminal stuff to give the appearance of a
more interactive display  that might not work well when read live, but
that's where the options come in I think.  You can probably suppress the
....... stuff and perhaps force more useful information?  (might also be
needed for the dumping to a file method..)  Wish I could try things but
life seldom cooperates lately!

Also, OT: Richard.. I have some petroglyph photos here if you're
interested.  Also can link you up with a lady here (the photographer) who
can show you locations for tons of them. If you're interested for your
pursuit of archaeological protection, or just interested period, let me
know.

On Sun, Nov 2, 2014 at 10:13 AM, Mark Wieder <mwieder at ahsoftware.net> wrote:

> Richard-
>
> Sunday, November 2, 2014, 8:59:25 AM, you wrote:
>
> >  > /usr/local/bin/wget --no-check-certificate --config=/etc/wgetrc -O-
> >  > --content-on-error -o /dev/null
>
> > The options for displaying progress in the terminal work well, but how
> > can we call that from LiveCode to obtain that progress info periodically
> > while the command is executing from the "shell" function?
>
> get shell("/usr/local/bin/wget <options>...
>
> in particular, the -O- error will give you the info that normally just
> goes to the screen. I use the --content-on-error argument to receive
> information even if wget runs into an error, and the -o /dev/null
> argument is because wget has an annoying habit of putting "..." into
> the output stream as a means of telling you it's still working. If
> you're getting the wget output as above then the "..." gets mixed in
> with the data, and the -o option sends the status data to /dev/null.
>
> try "wget --help" for a dizzying list of options
>
> > Is there a way to use "open process" for that?
>
> Probably, but shell does the job quite well.
>
> --
> -Mark Wieder
>  ahsoftware at gmail.com
>
> This communication may be unlawfully collected and stored by the National
> Security Agency (NSA) in secret. The parties to this email do not
> consent to the retrieving or storing of this communication and any
> related metadata, as well as printing, copying, re-transmitting,
> disseminating, or otherwise using it. If you believe you have received
> this communication in error, please delete it immediately.
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>