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.

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

Use Terminal for Help and Version Output #13728

Closed
StefanGreve opened this issue Aug 12, 2022 · 2 comments
Closed

Use Terminal for Help and Version Output #13728

StefanGreve opened this issue Aug 12, 2022 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@StefanGreve
Copy link

Description of the new feature/enhancement

If you run the help or version command for wt, a new window appears to display this information. I think it would make much more sense to write this information directly to terminal since this information (e.g. the version number) cannot be easily processed by other scripts.

image

Affected commands:

  1. wt --version
  2. wt --help

Proposed technical implementation details (optional)

In my opinion it would be better if the output of these commands would be displayed in the terminal directly. Frankly speaking, it is irritating that there are windows popping up every time I want to check which version of Windows Terminal I am on.

@StefanGreve StefanGreve added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Aug 12, 2022
@ghost ghost added 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 Aug 12, 2022
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #7258 for more discussion. That thread covers more of why this is a Hard problem

/dup #7258

@ghost
Copy link

ghost commented Aug 12, 2022

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Aug 12, 2022
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed 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 Aug 12, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants