Re: [exec] Executed command can't open file argument

2018-05-03 Thread Mark Trolley
On Thu, May 3, 2018 at 4:34 PM, sebb wrote: > On 3 May 2018 at 17:18, Mark Trolley wrote: > It may be that quotes are being added to the parameter - I assume the > file name does not have quotes. > > Quoting is necessary for protecting spaces on a shell

Re: [exec] Executed command can't open file argument

2018-05-03 Thread Martin Gainty
Mark- 1)get an OS that supports spaces in filenames 2)OR use quote to delimit file name e.g. "file name.ext" https://www.itl.nist.gov/div898/software/dataplot/refman1/auxillar/filequot.htm HTH Martin __ From: Mark

Re: [exec] Executed command can't open file argument

2018-05-03 Thread sebb
On 3 May 2018 at 17:18, Mark Trolley wrote: > I'm not sure how to respond to my own thread so I am hoping sending a > reply to my own sent message will do it. > > I experimented and discovered the problem is in the spaces in the > filename argument. If the file is renamed

Re: [exec] Executed command can't open file argument

2018-05-03 Thread Mark Trolley
I'm not sure how to respond to my own thread so I am hoping sending a reply to my own sent message will do it. I experimented and discovered the problem is in the spaces in the filename argument. If the file is renamed to not have spaces the execution succeeds. However, this doesn't work for my