passing arguments to system command

[scooter6 at gmail.com]

I figured it out -- it was my script that was sending the email -- thanks
for all that replied.....

Scott

On Tue, Oct 3, 2017 at 6:11 PM, Joan Sanchez via Filepro-list <
filepro-list at lists.celestial.com> wrote:

> It also depends on how you are referring to those arguments within your
> script. Maybe you are using $@ (without quotes) when you need to use "$@"
> (with quotes).
>
> Joan Sanchez
> Aljex Software, Inc.
> (732) 357-8700 x 166
> joan at aljex.com <mailto:joan at aljex.com>
> Aljex Signature
>
>
> On 10/3/2017 4:47 PM, scooter6--- via Filepro-list wrote:
>
>> Ok, so what I did was create two variables.....one is   aa(1,*)="\""
>> the other is  ab(30,allup)=cli(2)     (which cli(2) is a 30,allup field
>> from our client file)
>> I then passed to msgbox      "value is"<{aa{ab{aa        which properly
>> returned     "CLIENT NAME"    with the quotes...........
>> However, when I pass this same to my shell script, it no longer errors,
>> but
>> it only shows the value UP UNTIL the first space it encounters.........so
>> in this example, it just returns  CLIENT
>> I'm wanting to take the client name variable and have it included in the
>> subject line of an email that I send  @done  in processing.....everything
>> else works great except this part....
>>
>>
>>
>> On Tue, Oct 3, 2017 at 1:52 PM, Fairlight via Filepro-list <
>> filepro-list at lists.celestial.com> wrote:
>>
>> Another thing to keep in mind is which quotes you need.  You only need
>>> double quotes if 1) the argument will need shell variable interpolation,
>>> or
>>> 2) the string will contain other single quotes, such as apostrophes.
>>>
>>> If you can get away with single quotes, it becomes simpler still, since
>>> you
>>> won't need to escape them.
>>>
>>> As far as not working, I'd stuff everything into a variable, then msgbox
>>> it
>>> so you can see exactly what is being passed to system().
>>>
>>> m->
>>>
>>> On Tue, Oct 03, 2017 at 01:45:02PM -0400, scooter6 at gmail.com thus spoke:
>>>
>>>>     Hmm..not how I would have ever thought to do that... currently I
>>>> pass
>>>>     Â  <aa<ab<ac, etc......I would have assumed then I would have
>>>> neededÂ
>>>>     <"\"{ac{"\"    ?  But that didn't work...
>>>>     I'll give this a try....thanks Mark
>>>>
>>>>     On Tue, Oct 3, 2017 at 1:06 PM, Fairlight via Filepro-list
>>>>     <[1]filepro-list at lists.celestial.com> wrote:
>>>>
>>>>       aa = "/path/to/command" < "arg1" < "\"arg2 with spaces\"" < "arg3"
>>>>       system aa
>>>>       mark->
>>>>       On Tue, Oct 03, 2017 at 12:56:39PM -0400, scooter6--- via
>>>>       Filepro-list thus spoke:
>>>>
>>>>     > I have a process that triggers an email at the end and I pass
>>>>
>>> several
>>>
>>>>     > variables to my shell script
>>>>     > All of these parameters are short and contain  no spaces....
>>>>     >
>>>>     > How do I character escape a string I want to send my script that
>>>>     would have
>>>>     > spaces in it?
>>>>     > Meaning how would I send literal " (quotes) around a longer
>>>> variable
>>>>     that
>>>>     > has spaces in it?
>>>>     >
>>>>     >
>>>>     > thanks
>>>>     >
>>>>     > Scott
>>>>
>>>>       > -------------- next part --------------
>>>>       > An HTML attachment was scrubbed...
>>>>       > URL: <[2]http://mailman.celestial.com/pipermail/filepro-list/
>>>>       attachments/20171003/4e49eb59/attachment.html>
>>>>       > _______________________________________________
>>>>       > Filepro-list mailing list
>>>>       > [3]Filepro-list at lists.celestial.com
>>>>       > Subscribe/Unsubscribe/Subscription Changes
>>>>       > [4]http://mailman.celestial.com/mailman/listinfo/filepro-list
>>>>       >
>>>>       --
>>>>       Audio panton, cogito singularis.
>>>>       _______________________________________________
>>>>       Filepro-list mailing list
>>>>       [5]Filepro-list at lists.celestial.com
>>>>       Subscribe/Unsubscribe/Subscription Changes
>>>>       [6]http://mailman.celestial.com/mailman/listinfo/filepro-list
>>>>
>>>> References
>>>>
>>>>     1. mailto:filepro-list at lists.celestial.com
>>>>     2. http://mailman.celestial.com/pipermail/filepro-list/
>>>>
>>> attachments/20171003/4e49eb59/attachment.html
>>>
>>>>     3. mailto:Filepro-list at lists.celestial.com
>>>>     4. http://mailman.celestial.com/mailman/listinfo/filepro-list
>>>>     5. mailto:Filepro-list at lists.celestial.com
>>>>     6. http://mailman.celestial.com/mailman/listinfo/filepro-list
>>>>
>>> --
>>> Audio panton, cogito singularis.
>>> _______________________________________________
>>> Filepro-list mailing list
>>> Filepro-list at lists.celestial.com
>>> Subscribe/Unsubscribe/Subscription Changes
>>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>>
>>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <http://mailman.celestial.com/pipermail/filepro-list/attachm
>> ents/20171003/155d7589/attachment.html>
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at lists.celestial.com
>> Subscribe/Unsubscribe/Subscription Changes
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mailman.celestial.com/pipermail/filepro-list/attachm
> ents/20171003/e7cb550c/attachment.html>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20171003/c0890d0e/attachment.html>