Re: any tricks to make SHELL non blocking?

On Tue, Feb 6, 2018 at 3:28 PM, Warren Samples via use-livecode < use-livecode@lists.runrev.com> wrote: > >> > With all due respect, this is not all correct information. It is perfectly > valid to escape using single quotes (and double quotes) on the command line hmm, for spaces, that seems to

Re: any tricks to make SHELL non blocking?

On 02/06/2018 07:35 PM, hh via use-livecode wrote: You are obviously an expert with the shell/unix. Nothing of the sort, I'm just sharing some information I have collected from other sources and have found to work in this kind of situation :D Warren

Re: any tricks to make SHELL non blocking?

> Warren S. wrote: > The dictionary says: "On OS X systems, you can use the open process > command to start up an application, but not a Unix process. To work with > a Unix process, use the shell func instead." That makes me wonder if you > can only use shell() with ffmpeg. It is not quite

Re: any tricks to make SHELL non blocking?

On 02/05/2018 11:04 PM, Stephen Barncard via use-livecode wrote: I have this open sourced app ffmpeg and I need to copy the first file from a CD, convert it to a wav file, name it, and save it to a file on a hard drive. (the executable is located in the same folder as the stack, hence the ./ )

Re: any tricks to make SHELL non blocking?

On 02/06/2018 10:25 AM, Dr. Hawkins via use-livecode wrote: double quotes cause evaluation (for shell variables?), back quote (`) causes contents to execute. You seem to be using ', which is a literal. You have*SPACES* in file names. This*ALWAYS* leads to suffering. Quoting a filename does

Re: any tricks to make SHELL non blocking?

On Tue, Feb 6, 2018 at 12:03 PM, Stephen Barncard via use-livecode < use-livecode@lists.runrev.com> wrote: > Mike Bonner: I'll try the Open Process suggestion you made - again with > more syntax variations this time. thanks! > > Dr Hawkins - I don't have control over the name of the CD source

Re: any tricks to make SHELL non blocking?

Mike Bonner: I'll try the Open Process suggestion you made - again with more syntax variations this time. thanks! Dr Hawkins - I don't have control over the name of the CD source file.. 1 Audio Track.aiff the OS demuxes the data on the CD and gives them generic names. surely there must be a

Re: any tricks to make SHELL non blocking?

On Mon, Feb 5, 2018 at 9:46 PM, Mike Bonner via use-livecode < use-livecode@lists.runrev.com> wrote: > > > (./ffmpeg -i '/Volumes/Audio CD/1 Audio Track.aiff' '/Volumes/20160518 > KJAZ > > ARCHIVE MASTER/JULY - JAN 2017/20040315-2-JD0211b.wav' &) > double quotes cause evaluation (for shell

Re: any tricks to make SHELL non blocking?

seriously, back on topic... on mac -- El Capitan calling shell I have this open sourced app ffmpeg and I need to copy the first file from a CD, convert it to a wav file, name it, and save it to a file on a hard drive. (the executable is located in the same folder as the stack, hence the ./ ) so

Re: any tricks to make SHELL non blocking?

On Mon, Feb 5, 2018 at 2:18 PM, Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: > On 02/05/2018 12:02 PM, Dr. Hawkins via use-livecode wrote: > > disintegrated (and so did that plumber). >> > > !!! > > *shrug* So I'm a vengeful homeowner. :) -- Dr. Richard E. Hawkins,

Re: any tricks to make SHELL non blocking?

On 02/05/2018 12:02 PM, Dr. Hawkins via use-livecode wrote: disintegrated (and so did that plumber). !!! -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe,

Re: [OT] any tricks to make SHELL non blocking?

AAARRRGGGHHH!!! Bob S > On Feb 4, 2018, at 11:23 , J. Landman Gay via use-livecode > wrote: > > On 2/4/18 12:13 PM, prothero--- via use-livecode wrote: >> Totally ot, >> My mother in law had an iron drain deteriorate, with roots and cracks all >> through

[OT] Re: any tricks to make SHELL non blocking?

On 2/4/18 12:13 PM, prothero--- via use-livecode wrote: Totally ot, My mother in law had an iron drain deteriorate, with roots and cracks all through it, Not totally off-topic. If you drop a large enough shell into a pipe it will be blocking. -- Jacqueline Landman Gay |

Re: any tricks to make SHELL non blocking?

Totally ot, My mother in law had an iron drain deteriorate, with roots and cracks all through it, and Roto Rooter was able to ream it and put in some kind of epoxy liner, so nothing had to be dug up. Bill William Prothero http://es.earthednet.org > On Feb 4, 2018, at 7:53 AM, Dr. Hawkins via

Re: any tricks to make SHELL non blocking?

On Sat, Feb 3, 2018 at 4:51 PM, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > The Husband loves plumbing, it gives him the inspiration to learn all > kinds of new colorful words. He puts it off as long as possible to savor > the anticipation > There's nothing like

Re: any tricks to make SHELL non blocking?

The Husband loves plumbing, it gives him the inspiration to learn all kinds of new colorful words. He puts it off as long as possible to savor the anticipation. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com

Re: any tricks to make SHELL non blocking?

On 02/03/2018 02:31 PM, Richard Gaskin via use-livecode wrote: If everyone would just get over themselves and start using Linux we could all enjoy named pipes. :) After working on our kitchen plumbing for the last few days, I've got a few choice names for pipes. -- Mark Wieder

Re: any tricks to make SHELL non blocking?

Paul Dupuis wrote: > FYI we found that interapp communication via sockets is more reliable > cross-platform that via interprocess communication, but at some real > world customer sites, security setting can prohibit socket > communication even to the same computer where as IPC still works, so >

Re: any tricks to make SHELL non blocking?

On Fri, Feb 2, 2018 at 1:41 PM, Klaus major-k via use-livecode < use-livecode@lists.runrev.com> wrote: > > Any hints on how to make this NON blocking somehow? > I need a solution for Mac and Win. > > I don''t know about darkside machines, but on \begin{condescending snark} mac and other real

Re: any tricks to make SHELL non blocking?

> Way cool, dude! > Voll krass, Alter! :-) Yes. I once was also a young man with curly hair -- like you. are now ... ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your

Re: any tricks to make SHELL non blocking?

Hi Hermann, > Am 03.02.2018 um 00:35 schrieb hh via use-livecode > : > >> Klaus wrote: >> ... it WORKS, thanks a lot! > > How could you doubt that!? :-( sorry, really didn't mean it personally! ;-) > I never post things that I didn't test thoroughly, learned

Re: any tricks to make SHELL non blocking?

> Klaus wrote: > ... it WORKS, thanks a lot! How could you doubt that!? :-( I never post things that I didn't test thoroughly, learned that from 'bn'. In this case I looked into the script of my next Mac/Win/Linux/Raspi-stack "timeLapseCamera" which runs since four days without problems. I have

Re: any tricks to make SHELL non blocking?

On 2/2/2018 5:42 PM, Richard Gaskin via use-livecode wrote: > Paul Dupuis wrote: > > > I don't think you can use shell as non-blocking. You could use 'open > > process' to spawn your command line utility off as a subprocess which > > would be non blocking, but that approach has its own over head

Re: any tricks to make SHELL non blocking?

Hi Hermann, > Am 03.02.2018 um 00:02 schrieb Klaus major-k via use-livecode > : > > Hi Hermann, > >> Am 02.02.2018 um 23:53 schrieb hh via use-livecode >> : >> >> This is non-blocking: >> >> put tCommandLineUtility &&

Re: any tricks to make SHELL non blocking?

Hi Hermann, > Am 02.02.2018 um 23:53 schrieb hh via use-livecode > : > > This is non-blocking: > > put tCommandLineUtility && q(tGeneratedFile) into p0 > open process p0 for neither -- no need to close that > > Don't use quotes for the utility. > You have no

Re: any tricks to make SHELL non blocking?

Hello Hermann, > Am 02.02.2018 um 23:53 schrieb hh via use-livecode > : > > This is non-blocking: > > put tCommandLineUtility && q(tGeneratedFile) into p0 > open process p0 for neither -- no need to close that > > Don't use quotes for the utility. > You have no

Re: any tricks to make SHELL non blocking?

Hi Phil, > Am 02.02.2018 um 23:30 schrieb Phil Davis via use-livecode > : > > Run it in a different app that you communicate with via sockets? Or maybe run > that app as a process? > You said *any* hints, so... be careful what you ask for! :-) yep, get it! :-D

Re: any tricks to make SHELL non blocking?

This is non-blocking: put tCommandLineUtility && q(tGeneratedFile) into p0 open process p0 for neither -- no need to close that Don't use quotes for the utility. You have no feedback with that. That's the advantage of shell. > Klaus M. wrote: > Hi friends, > I have a command line utility which

Re: any tricks to make SHELL non blocking?

Paul Dupuis wrote: > I don't think you can use shell as non-blocking. You could use 'open > process' to spawn your command line utility off as a subprocess which > would be non blocking, but that approach has its own over head thing > to work around What additional overhead is incurred by

Re: any tricks to make SHELL non blocking?

I don't think you can use shell as non-blocking. You could use 'open process' to spawn your command line utility off as a subprocess which would be non blocking, but that approach has its own over head thing to work around On 2/2/2018 4:41 PM, Klaus major-k via use-livecode wrote: > Hi friends,

Re: any tricks to make SHELL non blocking?

Run it in a different app that you communicate with via sockets? Or maybe run that app as a process? You said *any* hints, so... be careful what you ask for! :-) Phil Davis On 2/2/18 1:41 PM, Klaus major-k via use-livecode wrote: Hi friends, I have a command line utility which will

any tricks to make SHELL non blocking?

Hi friends, I have a command line utility which will process a generated file like: ... get shell(q(tCommandLineUtility) && q(tGeneratedFile)) ... FYI: function q tString return QUOTE & tString & QUOTE end q Any hints on how to make this NON blocking somehow? I need a solution for Mac and