wt.exe should accept env vars on the commandline #20515

Open
opened 2026-01-31 07:16:16 +00:00 by claunia · 0 comments
Owner

Originally created by @zadjii-msft on GitHub (Sep 20, 2023).

forked from #15496

wt -E foo=bar to manually pass env vars to the NewTerminalArgs. This'll let a caller manually pass env vars on the commandline. Great!

builds off the work in #15082. Basically, each of the -E foo=bar args would get collected by the arg parser, then eventually passed to TerminalSettings::CreateWithNewTerminalArgs. We'd layer them on top of anything from the profile.

open questions:

  • syntax?
  • What if I want to pass -E foo=%bar%, where bar is something defined in the profile's env block, but not the current one?
    • IMO we can just say no to this. This seems impossible, and also why?
Originally created by @zadjii-msft on GitHub (Sep 20, 2023). forked from #15496 > `wt -E foo=bar` to manually pass env vars to the `NewTerminalArgs`. This'll let a caller manually pass env vars on the commandline. Great! builds off the work in #15082. Basically, each of the `-E foo=bar` args would get collected by the arg parser, then eventually passed to `TerminalSettings::CreateWithNewTerminalArgs`. We'd layer them on top of anything from the profile. open questions: * [ ] syntax? * [ ] What if I want to pass `-E foo=%bar%`, where `bar` is something defined in the profile's env block, but not the current one? - IMO we can just say no to this. This seems impossible, and also _why?_
claunia added the Issue-TaskProduct-TerminalArea-Commandline labels 2026-01-31 07:16:17 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20515