any tricks to make SHELL non blocking?

Dr. Hawkins dochawk at gmail.com
Tue Feb 6 21:58:13 EST 2018


On Tue, Feb 6, 2018 at 3:28 PM, Warren Samples via use-livecode <
use-livecode at 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 be correct.

But that just proves the point; spaces in filenames are evil :)

I learned unix on a cluster PDP-11 over three decades ago, and I'm still
off on this.

There are other things, however, notably environmental variables, that do
not get escaped in the weak quoting of double quotes.



> 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"


careful;  OSX defaults to tcsh, not bash.


-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462



More information about the Use-livecode mailing list