We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug %~ variables such as %~dp0 in cmd.exe are documented only in the "Variable substitution" section on the page for the for statement.
for
However, they work outside a for statement as well. See, for example, this hack for allowing a graphical subsystem program to be run from the command-line and have the command interpreter wait for it to complete, rather than running it in the background as cmd.exe does with graphical subsystem applications: https://github.com/foxx1337/Metamorph. The script itself is at https://github.com/foxx1337/Metamorph/blob/master/Metamorph/mm.cmd.
The text was updated successfully, but these errors were encountered:
FYI @Xelu86.
Sorry, something went wrong.
No branches or pull requests
Describe the bug
%~ variables such as %~dp0 in cmd.exe are documented only in the "Variable substitution" section on the page for the
for
statement.However, they work outside a
for
statement as well. See, for example, this hack for allowing a graphical subsystem program to be run from the command-line and have the command interpreter wait for it to complete, rather than running it in the background as cmd.exe does with graphical subsystem applications: https://github.com/foxx1337/Metamorph. The script itself is at https://github.com/foxx1337/Metamorph/blob/master/Metamorph/mm.cmd.The text was updated successfully, but these errors were encountered: