To add new values to path, you can now enter setx path "%path% yournewpath" /m To do this, hit the Meta(Windows) key, type cmd and hit CTRL+ SHIFT+ ENTER and confirm the UAC dialog. To do this, you first need to bring up a command line with admin privileges. You can also add a value to the system variable PATH. If you don't have it defined yet, do so by typing: SETX PATH yourpath You can have a PATH user environment variable that happily coexists with the system PATH variable.
You'll have to be a bit careful though, it's easy to make a mess of your variables with SETX.īy default, you change user variables.
Its syntax differs a lot from SET, but it's also powerful. Unlike in other versions of Windows, it comes built-in with Windows 7. To change environment variables permanently, you have to use the SETX command in the Windows command line.
There, you can either edit the system variable PATH (bottom list) or add/edit a new PATH variable to the user environment variables. From there, click "Environment variables". On Windows 7, just type "system" in the META-Prompt and you'll see an entry "Edit the System Environment Variables". UPDATED ANSWER - Defining permanent environment variables using the CLI and GUI - Scroll down for the original answer ANT-HOME), commit, check if it's expanded, if it is, go on with the next level commit, check. That means: Try deleting all variables you want to nest into each other (including calls from PATH to your user-defined variables), and then start up from scratch. The only viable workaround I found is adding variables recursion level by recursion level. I've already run into the same problem and found no clear, reproducible circumstances - the recursion level at which expansion fails is not consistent, special characters don't seem to play a role, etc. There's some general problems concerning variable expansion in Windows. UPDATE NO.2 - Now to the actual question: Why do nested, user-created variables fail to expand?
0 kommentar(er)
