Skip to content

MEGATHREAD: Commandline Args Follow-Up Work #4632

Open
1 of 3 issues completed
Open

Description

Reference

Untriaged Bugs/Features

1.0 Bugs

The Help Dialog

Post 1.0 features

2.0 Bugs

Backlog

Discussion

Other related discussion

Activity

  1. ghost added
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Feb 18, 2020
  2. ghost added
    Needs-Tag-FixDoesn't match tag requirements
    on Feb 18, 2020
  3. ghost removed
    Needs-Tag-FixDoesn't match tag requirements
    on Feb 18, 2020
  4. added and removed
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Feb 18, 2020
  5. DHowett-MSFT commented on Feb 21, 2020

    @DHowett-MSFT
    Contributor

    I've moved #4619, #4618 and and #4602 into the v1.0 milestone.

  6. Karl-WE commented on Feb 23, 2020

    @Karl-WE

    for any new args please consider reading and support this feature request before it get's out of control / focus.
    Reference #4601

  7. WSLUser commented on Apr 23, 2020

    @WSLUser
    Contributor

    Mike Griese (@zadjii-msft) Please add #5494 to the list to add -v, --version to the list of args. All other Windows apps (linux apps too, but different arg) allow viewing the version via CLI (even if we need it to simply open up the About page).

  8. ghost added a commit that references this issue on Jun 1, 2020
  9. Guiorgy commented on Aug 19, 2020

    @Guiorgy

    Windows commandline args are usually /fooBar but ours are --fooBar and that's weird

    Is there an open discussion for this, or is this only internal for now?

  10. zadjii-msft commented on Aug 19, 2020

    @zadjii-msft
    MemberAuthor

    Guiorgy (@Guiorgy) I don't think there's a current nogoing discussion, but there's mot really any chance that we'll change this, considering that 1.0 has already shipped with --fooBar args.

    As we discovered over in #4601 (comment), it turns out that /fooBar style params will actually secretly work as well, but we're not officially documenting that in case CLI11 ever changes that out from underneath us.

  11. Guiorgy commented on Aug 19, 2020

    @Guiorgy

    Mike Griese (@zadjii-msft) Oh wow, it does work! 😃
    Anyways, glad to hear that -- isn't going anywhere. Personally, I hope you officially support both at some point.

  12. ghost added a commit that references this issue on Oct 14, 2020
  13. rashil2000 commented on Jul 23, 2021

    @rashil2000
    Contributor

    Sorry, I couldn't find any documentation, but are --height or --width options for launching new window planned/supported?

    (Use case: a desktop shortcut for opening neovim in WT. I'd like that window to be larger than what I have normally set for the terminal in settings.json through the initialRows and initialCols options)

  14. honeylizard commented on Feb 16, 2022

    @honeylizard

    After opening a WLS profile (e.g. Ubuntu), is there anyway to pass Unix style commands?

    Running wt.exe new-tab -p Ubuntu cd /example/path opens the tab, but the terminal shows the error

    [error 0x80070002 when launching 'cd /example/path']

    All the examples I've found so far show how to run Windows commands after a new-tab call, but nothing on unix/linux commands...

  15. htcfreek commented on Sep 29, 2023

    @htcfreek
    Contributor

    und so far show how to run Windows commands after a new-tab call, but nothing on unix/linux commands...

    Same for me with PowerShell or other profiles. I opened the issue #16062 .

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

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions