command line - windows env variables not resolving
2014-04
I have the following env variables:
VIM_HOME: %ProgramFiles(x86)%\Vim\vim74
CMD: %USERPROFILE%\cmd
PATH: ...%CMD%;%VIM_HOME%;...
C:\Users\me\cmd\vim.bat
@echo off
start vim.exe %*
Prompt:
> echo %ProgramFiles(x86)%
C:\Program Files (x86)
> echo %USERPROFILE%
C:\Users\me
> echo %CMD%
C:\Users\me\cmd
> echo %VIM_HOME%
C:\Program Files (x86)\Vim\vim74
All good so far...
> echo %PATH%
...C:\Users\me\cmd;%VIM_HOME%;...
%VIM_HOME%
not resolved, but %CMD%
was? And consequently:
> vim
'vim.exe' is not recognized as an internal or external command, operable program or batch file.
I don't understand?
Not even sure how to word this "answer," so if you feel you can word it differently, or add something valuable, please do so:
After many attempts (see the comments
section under the question) to figure out why the VIM_HOME variable was not working, a suggestion was made to rename the variable from VIM_HOME to _VHOME. The end-user confirmed that this change allowed them to launch VIM via their batch script without an issue. Still, there was no "real" reason why the VIM_HOME variable wouldn't work, unless it's a reserved internal variable to VIM.
So, my path variable (System->Adv Settings->Env Vars->System->PATH) is set to:
C:\Python26\Lib\site-packages\PyQt4\bin;
%SystemRoot%\system32;
%SystemRoot%;
%SystemRoot%\System32\Wbem;
%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;
C:\Python26\;
C:\Python26\Scripts\;
C:\cygwin\bin;
"C:\PathWithSpaces\What_is_this_bullshit";
"C:\PathWithSpaces 1.5\What_is_this_bullshit_1.5";
"C:\PathWithSpaces (2.0)\What_is_this_bullshit_2.0";
"C:\Program Files (x86)\IronPython 2.6";
"C:\Program Files (x86)\Subversion\bin";
"C:\Program Files (x86)\Git\cmd";
"C:\Program Files (x86)\PuTTY";
"C:\Program Files (x86)\Mercurial";
Z:\droid\android-sdk-windows\tools;
Although, obviously, without the newlines.
Notice the lines containing PathWithSpaces
- the first has no spaces, the second has a space, and the third has a space followed by a parenthesis.
Now, notice the output of this batch file:
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\>vcvars32.bat
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin>"C:\Program Files (x86
)\Microsoft Visual Studio 9.0\Common7\Tools\vsvars32.bat"
Setting environment for using Microsoft Visual Studio 2008 x86 tools.
\What_is_this_bullshit_2.0";"C:\Program was unexpected at this time.
C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin> set "PATH=C:\Pro
gram Files\Microsoft SDKs\Windows\v6.0A\bin;C:\Python26\Lib\site-packages\PyQt4\
bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\
WindowsPowerShell\v1.0\;C:\Python26\;C:\Python26\Scripts\;C:\cygwin\bin;"C:\Path
WithSpaces\What_is_this_bullshit";"C:\PathWithSpaces 1.5\What_is_this_bullshit_1
.5";"C:\PathWithSpaces (2.0)\What_is_this_bullshit_2.0";"C:\Program Files (x86)\
IronPython 2.6";"C:\Program Files (x86)\Subversion\bin";"C:\Program Files (x86)\
Git\cmd";"C:\Program Files (x86)\PuTTY";"C:\Program Files (x86)\Mercurial";Z:\dr
oid\android-sdk-windows\tools;"
or specifically the line:
\What_is_this_bullshit_2.0";"C:\Program was unexpected at this time.
So, what is this bullshit?
Specifically:
- Directory in path that is properly escaped with quotes, but with no spaces = fine
- Directory in path that is properly escaped with quotes, and has spaces but no parenthesis = fine
- Directory in path that is properly escaped with quotes, and has spaces and has a parenthesis = ERROR
Whats going on here? How can I fix this? I'll probably resort to a junction point to let my tools still work as workaround, but if you have any insight into this, please let me know :)
This can happen if there are unescaped parentheses in a line inside a "block" (which also uses parentheses for delimiting).
You can usually fix it by turning on delayed expansion and use variables with !var!
instead of %var%
. There isn't much more advice I could give without seeing the code.
There should either (a) not be any quotes in the MS-Windows PATH environmental variable (MS-DOS PATH command) or (b) there should be quotes surrounding the entire expression following the SET command (MS-DOS SET command). Unfortunately, this is not very well documented by MS, although they do state that if quotes are used, they will be included in the value of the variable (MS Command Line Reference).
$ SET BLAH="blah blah(1)"
$ ECHO %BLAH%
"blah blah(1)"
$ SET BLAH=blah blah(1)
$ ECHO %BLAH%
blah blah(1)
This can cause problems that are inconsistent and therefore difficult to diagnose. For example if your path includes "C:\Python27", your machine will say "'python' is not recognized as an internal or external command, operable program or batch file." when you try to execute python. However some libraries may still be available.
You do not need to "escape" spaces or parentheses. If you need to escape special characters, then put quotes around the entire expression, including the variable name.
SET "PATH=%PATH%;C:\Program Files (x86)\path with special characters"
or you can use parentheses too.
(SET PATH=%PATH%;C:\Program Files (x86)\path with special characters)
However, there probably are not any characters that are valid pathnames, that would cause a problem with the SET command.
Note for Windows users on 64-bit systems
Progra~1 = 'Program Files' Progra~2 = 'Program Files(x86)'
https://confluence.atlassian.com/display/DOC/Setting+the+JAVA_HOME+Variable+in+Windows
Joey in his answer says
This can happen if there are unescaped parentheses in a line inside a "block" (which also uses parentheses for delimiting).
and that's true. If there are unescaped parentheses one should, well escape them. That's what I did; I replaced
set PATH=some_path;%PATH%
with
set PATH="some_path;%PATH%"
and this solved the problem.
I've experienced something similar. Microsoft explains the issue here: http://support.microsoft.com/kb/329308
Basically, instead of changing the Path variable via System->Adv Settings->Env Vars->System->PATH, try
My Computer->Manage->Computer Management (local)-> Properties-> Advanced-> Environment variables-> Settings
In Windows 8 I've found very little success with any of these methods. Parentheses do not work, quotes work, but the "path" you modify this way isn't the path that gets used for locating executables, instead cmd
still seems to be using the system path it inherited when you opened the window.
example: after determining the processor architecture, I want to add a couple of paths to the PATH environment variable. Actually, even just adding them temporarily would work since I only need them while a batch file is running. But that doesn't even work.
echo %path%
displays the system PATH at the time the cmd
was launched.
set path="%path%;%programfiles(x86)%\company\program\subdir"
works but now %path%
contains everything surrounded by quotes, and if I try to run a program in subdir from somewhere else, it fails. Using parentheses around the whole thing instead of quotes does not work.
Another thing I've noticed is that the same command will work if entered interactively in cmd
, but not if encountered in a batch file. That's frightening. Yet another oddity is the intermittent loss of the last character of an environment variable's value! Another inconsistency is with third party programs: some can handle a %var%
as a parameter, others don't.