Unlike other "command variables" they're going into the environment.
vefatica May 20, 2008 12,167 133 Syracuse, NY, USA Oct 4, 2017 #1 Unlike other "command variables" they're going into the environment.
rconn Administrator Staff member May 14, 2008 12,556 167 Oct 4, 2017 #2 vefatica said: Unlike other "command variables" they're going into the environment. Click to expand... That's right - except that they're not command variables, since they're not associated with any command.
vefatica said: Unlike other "command variables" they're going into the environment. Click to expand... That's right - except that they're not command variables, since they're not associated with any command.
vefatica May 20, 2008 12,167 133 Syracuse, NY, USA Oct 4, 2017 #3 rconn said: That's right - except that they're not command variables, since they're not associated with any command. Click to expand... The help says Code: @LINES also sets two command variables: Can't they be internal?
rconn said: That's right - except that they're not command variables, since they're not associated with any command. Click to expand... The help says Code: @LINES also sets two command variables: Can't they be internal?
rconn Administrator Staff member May 14, 2008 12,556 167 Oct 5, 2017 #4 vefatica said: The help says Code: @LINES also sets two command variables: Can't they be internal? Click to expand... No, they can't. Why does it matter to you?
vefatica said: The help says Code: @LINES also sets two command variables: Can't they be internal? Click to expand... No, they can't. Why does it matter to you?
