.envtc and the TEMP environment variable

[Joe Caverly]

With DIRENV on,
I have an .envtc file stored on my RAMDisk,
which is drive R:\

The DIRENV and .envtc were introduced in Version 30.

Take Command / TCC Help v. 32

jpsoft.com

The contents of the .envtc file on my R:\ drive;

R:\>type .envtc
temp=r:\temp

On a drive other than R:\, my TEMP environment variable points to;

TEMP=C:\Users\jlcav\AppData\Local\Temp

When I switch to drive R:\, the TEMP environment variable becomes;

R:\>set temp
r:\temp

When I switch to a drive other than R:\, the TEMP environment variable becomes;

E:\Utils>set temp
TCC: Not in environment "temp*"

My workaround to this issue,
is to use SETLOCAL before switching to my R:\ drive.

E:\Utils>set temp 
C:\Users\jlcav\AppData\Local\Temp

E:\Utils>setlocal 

E:\Utils>set temp 
C:\Users\jlcav\AppData\Local\Temp

E:\Utils>r: 

R:\>set temp 
r:\temp

R:\>e: 

E:\Utils>set temp 
TCC: Not in environment "temp*"

E:\Utils>endlocal 

E:\Utils>set temp
C:\Users\jlcav\AppData\Local\Temp

Posting this mainly for my future reference,
but thought others might find it useful.

Joe

 

[vefatica]

When I switch to a drive other than R:\, the TEMP environment variable becomes;

E:\Utils>set temp
TCC: Not in environment "temp*"

Don't you think TCC should reset it to the default? [Suggestions?]

 

[Joe Caverly]

No, I think it is okay.

I think that the documentation should be updated
to include what happens to an environment variable,
once it goes out of scope,
due to an .envtc file.

That is,
the environment variable gets deleted from the environment.

Documentation should include the work-around with SETLOCAL/ENDLOCAL.

Joe