any tricks to make SHELL non blocking?

Warren Samples warren at warrensweb.us
Tue Feb 6 18:28:02 EST 2018


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 not make it ok; it's still multiple words. If you
> want to keep such evil names, you'll have to escape those spaces with \
>   (backslash).

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 and it works inside a LC shell function.

Just to save time, here are some sources for verification:

https://www.tech-otaku.com/mac/file-folder-paths-os-x-terminal/

http://wiki.bash-hackers.org/syntax/quoting (see "Weak quoting" and 
"Strong quoting")

Warren




More information about the Use-livecode mailing list