Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

-d CLI parameter is not in the command list #8265

Closed
saschanaz opened this issue Nov 13, 2020 · 4 comments
Closed

-d CLI parameter is not in the command list #8265

saschanaz opened this issue Nov 13, 2020 · 4 comments
Labels
Issue-Question For questions or discussion Needs-Tag-Fix Doesn't match tag requirements Resolution-Answered Related to questions that have been answered

Comments

@saschanaz
Copy link

saschanaz commented Nov 13, 2020 •
edited
Loading

Environment

Windows build number: 10.0.19042.0
Windows Terminal version (if applicable): 1.4.3141.0

Steps to reproduce

wt -h

Expected behavior

-d should be there, or at least "see also wt new-tab -h".

Actual behavior

image

(Why a popup instead of stdout?)
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Nov 13, 2020
@DHowett
Copy link
Member

DHowett commented Nov 13, 2020

where is -d

It is an argument to "new-tab" and "split-pane" (the subcommands)
image

why a dialog

It's horrible.
More info in the "displaying output in a dialog" section here.

@DHowett DHowett closed this as completed Nov 13, 2020
@DHowett DHowett added Issue-Question For questions or discussion Resolution-Answered Related to questions that have been answered and removed Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Nov 13, 2020
@ghost ghost added the Needs-Tag-Fix Doesn't match tag requirements label Nov 13, 2020
@saschanaz
Copy link
Author

at least "see also wt new-tab -h".

How about this part?

@DHowett
Copy link
Member

DHowett commented Nov 13, 2020

As we add more subcommands, that's going to grow to be a very long list... isn't it?

@saschanaz
Copy link
Author

As we add more subcommands, that's going to grow to be a very long list... isn't it?

My current assumption is that the optional subcommand defaults to new-tab, maybe worth to make it clear so that I can try wt new-tab -h. Not sure how more subcommands would make it longer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Question For questions or discussion Needs-Tag-Fix Doesn't match tag requirements Resolution-Answered Related to questions that have been answered
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DHowett @saschanaz