[purpose]
This simple command sequence runs expected in the Windows' CMD shell:
dir & echo hello
will list the files and directories and echo the string.
However, the following command sequence does not run as expected (at least by me):
C:\Users\Administrator>set name=value & echo %name%
%name%
C:\Users\Administrator>echo %name%
value
C:\Users\Administrator>
As we can see, the first echo cannot get the environment. Could you help to comment? Any comment will be appreciated!
PS: OS:Windows 7 X64 Home Pre
Your result is due to the fact that %name% is expanded during the parsing phase, and the entire line is parsed at once, prior to the value being set.
You can get the current value on the same line as the set command in one of two ways.
1) use CALL to cause ECHO %NAME% to be parsed a 2nd time:
I put a
^
between the percents just in case name was already defined before the line is executed. Without the caret, you would get the old value.Note: your original line had a space before the
&
, this space would be included in the value of the variable. You can prevent the extra space by using quotes:set "name=value" &...
2) use delayed expansion to get the value at execution time instead of at parse time. Most environments do not have delayed expansion enabled by default. You can enable delayed expansion on the command line by using the appropriate CMD.EXE option.
Delayed expansion certainly can be used on the command line, but it is more frequently used within a batch file. SETLOCAL is used to enable delayed expansion within a batch file (it does not work from the command line)
You can also use
cmd /V /C
(with/V
to enable delayed expansion).That is great to set an environment variable for just one command in Windows
cmd.exe
:Note the usage of double-quotes in
set "name=value"
to avoid the extra space aftervalue
.For instance, without double-quotes:
You would need to think to remove the space between
value
and&&
:But using double-quotes makes the assignment more explicit.