INTERNAL Command anomaly

[Joe Caverly]

     _x64: 1
   _admin: 1
_elevated: 1

TCC  32.10.21 x64   Windows 10 [Version 10.0.19045.4529]
BuildNumber  Caption                   CSDVersion  OSArchitecture  Version
19045        Microsoft Windows 10 Pro              64-bit          10.0.19045

22H2

I have my temp folder;

E:\Utils>set temp
r:\temp

I can use the dir command to see if the file exists;

E:\Utils>dir %temp\hbcode.hb

 Volume in drive R is unlabeled    Serial number is 6edd:8cb4
 Directory of  R:\temp\hbcode.hb

2024-06-17  12:21             159  hbcode.hb

This works;

E:\Utils>*list %temp\hbcode.hb

This does not work;

E:\Utils>internal list %temp\hbcode.hb
TCC: (Sys) The system cannot find the path specified.
 "E:\Utils\%temp\hbcode.hb"

Internal seems to think that %temp is in my current directory,
which is E:\Utils.

This works;

E:\Utils>internal list r:\temp\hbcode.hb

This does not work;

E:\Utils>internal dir %temp\hbcode.hb

 Volume in drive E is New Volume   Serial number is 2c3e:6d62
TCC: (Sys) The system cannot find the file specified.
 "E:\Utils\%temp\hbcode.hb"
                   0 bytes in 0 files and 0 dirs

Internal seems to think that %temp is in my current directory,
which is E:\Utils.

Joe

 

[vefatica]

More like it isn't expanding environment variables, eh? The help doesn't mention that. I wonder if it's WAD.

v:\> internal dir %temp

 Volume in drive V is DATA         Serial number is 6e8a:6d1f
TCC: (Sys) The system cannot find the file specified.
 "V:\%temp"

 

[Charles Dye]

It isn't doing any expansion at all....

C:\>echo %@upper[hello, world!]
HELLO, WORLD!

C:\>internal echo %@upper[hello, world!]
%@upper[hello, world!]

C:\>

 

[rconn]

INTERNAL doesn't expand variables because the user who requested it didn't ask for variable expansion. If you want it, please post it in the Suggestions Forum.