You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 5, 2025. It is now read-only.
Our existing command-line composition is somewhat primitive, and is an opportunity for some more sophisticated design. Some things to consider:
It assumes blank spaces between switches/params. Some apps don't like a space (eg /s:123 as opposed to /s 123).
We only support PID and HWND parameters. Consider process name, executable path, aumid, window title.
We should probably allow the user to type in a command-line - this way its completely open-ended and not constrained to our notion of a command-line. If we do this, we'd want to support named variable substitutions, something like: /abc /foo /p{pid} /w{hwnd}.
Scenario
As part of this, we also need to support other activation mechanisms beyond command-line args. For example, protocol activation, appExecutionAlias, file-type association.