Skip to content

startupActions not run when in elevated window #13929

Open

Description

@svict4

Windows Terminal version

4.14.2282.0

Windows build number

10.0.22000.0

Other Software

No response

Steps to reproduce

  1. Add a startupAction in the settings.json at the top level
{
  "$help": "https://aka.ms/terminal-documentation",
  "startupActions": "new-tab; new-tab",
  ...
}
  1. Add the elevate property to a profile, such as the defaults profile
...
  "profiles": {
    "defaults": {
      "colorScheme": "Tango Dark",
      "elevate": true,
      ...
    },
    "list": [ ... ]
  }
...
  1. See that the startupActions are not respected.
  2. See that by commenting/removing the elevate property, that it runs the startupActions

Expected Behavior

That the arguments in startupActions are run, even in elevated window

Actual Behavior

startupActions are ignored/not run

Activity

  1. ghost added
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Sep 6, 2022
  2. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on Sep 6, 2022
  3. changed the title [-]startupActions not run when elevate[/-] [+]startupActions not run when run in elevated window[/+] on Sep 6, 2022
  4. changed the title [-]startupActions not run when run in elevated window[/-] [+]startupActions not run when in elevated window[/+] on Sep 6, 2022
  5. zadjii-msft commented on Nov 7, 2022

    @zadjii-msft
    Member

    We'll need to come up with a proper design for this.

    Opening an elevated "Foo" profile triggering the creation of a elevated window isn't going to hit startupActions ever. In that case, the "startup actions" has been effectively replaced by a single action - "open a tab with Foo".

    • Maybe we need an "open elevated window" action, that just opens wt without any actions. That would default to just startupActions.
    • Maybe we need a separate elevatedStartup for actions to run on startup of an elevated window. These would then be different from startupActions.
    • There's also The Terminal needs a commandline argument to open the window elevated #12191 - that could be combined with the command palette's commandline mode for a --elevate nt ; sp command to run specific actions in an elevated window.
  6. added
    Issue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.
    Area-SettingsIssues related to settings and customizability, for console or terminal
    and removed
    Issue-BugIt either shouldn't be doing this or needs an investigation.
    on Nov 7, 2022
  7. ghost removed
    Needs-Tag-FixDoesn't match tag requirements
    on Nov 7, 2022
  8. removed
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Mar 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-SettingsIssues related to settings and customizability, for console or terminalIssue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.Product-TerminalThe new Windows Terminal.

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions