Traditional Windows Run dialog (also search feature in the start menu) supports auto-completion with the environment variables. (For example, traditional run dialog understands the meaning of %windir%.) I think this is essential to replace those two features.
Case 1. For example, when I type "%windir%" in the text box, auto-suggestion automatically populates the open folder action.
Case 2. When I type "%comspec%" in the text box, auto-suggestion understands that this environment variable points out to a command-line interpreter, and user can open the app.
Case 3. When I type "%comspec% /k echo Hello, World!", auto-suggestion understands that this environment variable points out to command-line interpreter, and the user can open the app. Plus, the following parameter should propagate to the app and the console displays the message "Hello, World!" on the screen.
Case 4. This is not an environment variable case, but it requires for the Windows Terminal scenario. When I type the "wt" alias in the traditional interfaces, it launches successfully the new Windows Terminal app. Also, "wt %comspec%" will run the default command-line interpreter inside the Windows Terminal.
@rkttu you can currently do all of the scenarios you mentioned above in PowerToys Run by adding > at the beginning of your search query. For example, > %comspec% or > %windir%
@jyuwono Any chance for supporting PowerShell syntax variables?
@antonwnk please create a separate feature suggestion so we can keep track of it. It will also be helpful if you can add some more details in the issue (things like, what's the scenario you're trying to do, maybe with some examples)
@saahmedm this is merged and thus done :).
In the 0.25 release. https://github.com/microsoft/PowerToys/releases/tag/v0.25.0
Most helpful comment
@rkttu you can currently do all of the scenarios you mentioned above in PowerToys Run by adding
>at the beginning of your search query. For example,> %comspec%or> %windir%