2010/5/10 Steve Vinoski <vinoski@ieee.org>
OK, thanks for checking it; I've now pushed it up to github. This
solution will work for the case you provided, which is very very much
the normal case, but if anyone ever wanted to pass something like

--erlargs "-env NAME O'Keeffe"

where the name or value contains a single quote, it will still fail.
This case and the case where either name or value contains a double
quote are also fixable, but I figured they'd be so rare they're not
worth cluttering the code to handle them.

--steve

On Sun, May 9, 2010 at 5:40 PM, Andrew Yanovsky <buricchio@gmail.com> wrote:
> I see, he is! Hats off to Steve Vinoski!
>
>>
>> Well what do you know, that's just what I called for, a /bin/sh
>> wizard. Hats off!
>>
>> /klacke
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Erlyaws-list mailing list
>> Erlyaws-list@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/erlyaws-list
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Erlyaws-list mailing list
> Erlyaws-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/erlyaws-list
>
>

------------------------------------------------------------------------------

_______________________________________________
Erlyaws-list mailing list
Erlyaws-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlyaws-list

wouldn't  help it to escape this quotes with an \ if someone want to use them?

for example
   --erlargs "-env NAME O\'Keeffe"