Skip to content

NewTab won't leave the Command Palette #7441

Closed

Description

Environment

Windows build number: 10.0.19042.0
Windows Terminal version : 1.3.2382.0

Steps to reproduce

Add the following to your settings.json:

{ "name": null, "command": { "action": "newTab", "commandline": "wsl.exe" }, "keys": "f2" }

Expected behavior

This entry does not appear in the Command Palette.

Actual behavior

It appears in the Command Palette after explicitly setting "name" to null.

Activity

  1. added
    Issue-BugIt either shouldn't be doing this or needs an investigation.
    Area-UserInterfaceIssues pertaining to the user interface of the Console or Terminal
    on Aug 28, 2020
  2. ghost added
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Aug 28, 2020
  3. DHowett commented on Aug 28, 2020

    @DHowett
    Member

    oh no, this is another instance where we need to know the difference between null and ""!

    Except not in JSON. In Command.cpp:33-66

  4. removed
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Aug 28, 2020
  5. Don-Vito commented on Dec 10, 2020

    @Don-Vito
    Contributor

    Mike Griese (@zadjii-msft), Dustin L. Howett (@DHowett) - so this one is broken for 4 months.. and actually I am not sure when it really worked last time for commands that have action args 😊 Right now I don't see any evidence it ever worked 🤔

    So.. I am not sure if it is acceptable.. but cannot we simply replace this mechanism with something more explicit and parse-able. Like adding a dedicated field (aka "hideFromPalette")? Since I am not sure we can call it breaking compatibility

  6. zadjii-msft commented on Dec 11, 2020

    @zadjii-msft
    Member

    FYI future readers: #8402 has more investigation in it too.

    Yea, I think the "name": null idea for hiding came about long before auto-generated names did, so now hiding with a null name seems weird.

    I'm almost wondering how important hiding default commands is in the first place. It doesn't really seem like we've gotten requests for it. It's not like having default keybindings, where their presence might impact other apps.

    That would certainly make the design easier. If we didn't need to worry about hiding defaults, we could focus on just hiding commands defined by the user.

  7. atimholt commented on Dec 13, 2020

    @atimholt

    For what it's worth, I'm always for as much customizability as possible. The presence of commands that one has long decided they're never going to use creates a measure of noise and, worse, can often hinder "fluent" use by necessitating more keystrokes for the fuzzy-find search.

  8. ghost added
    In-PRThis issue has a related PR
    on Apr 16, 2021
  9. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on May 5, 2021
  10. added a commit that references this issue on May 5, 2021
    22fd06e
  11. ghost removed
    In-PRThis issue has a related PR
    on May 5, 2021
  12. ghost added
    Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.
    on May 5, 2021
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-CmdPalCommand Palette issues and featuresArea-UserInterfaceIssues pertaining to the user interface of the Console or TerminalIssue-BugIt either shouldn't be doing this or needs an investigation.Needs-Tag-FixDoesn't match tag requirementsProduct-TerminalThe new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions