! set me=Andy && Command Prompt screen flashes
?GETENV("me") && ''
i.e the environment variable lasts only the duration of the command
window (shell) - the same is true if you run a Command Prompt.
On 29/04/2014 01:30, Gene Wirchenko wrote:
At 05:47 2014-04-28, Man-wai Chang <[email protected]> wrote:
You can't add environment variables into a sub-shell, I believe.
Your belief is incorrect. My debugging code in the batch file
included echoing the environment variable value that I had set, and up
to the point of failure, they were set.
I might have run into some limit on how much environment space I
can use, and I was hoping someone could tell me if this is the case
and what to do about it.
What if you use a text file instead to store and pass parameters?
I do not know how to extract the parameters in the batch file.
How would one do this?
I decided to reorder the parameters, because I found that I have
to have multiple parameters for multiple attachments. With that, I
can no longer simply check the number of parameters.
Another trick is to programmatically generate the whole batch file
with parameters stored, then execute it.
I suppose so, but I prefer not to do that. It would be a pain to
debug.
Sincerely,
Gene Wirchenko
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
