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

Feature Request: More integration with Windows features. #2825

Open
stereokai opened this issue Sep 20, 2019 · 6 comments
Open

Feature Request: More integration with Windows features. #2825

stereokai opened this issue Sep 20, 2019 · 6 comments
Labels
Area-User Interface Issues pertaining to the user interface of the Console or Terminal Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Cmd.exe The issue is related to the legacy command interpreter, CMD.exe. Product-Powershell Issues in the modern command interpreter, Powershell.exe.
Milestone

Comments

@stereokai
Copy link

stereokai commented Sep 20, 2019

More integration with Windows features

Add commands to interact with standard Windows features. Metro Notifications, systray messages, Message boxes, and maybe even window actions. (close/minimize other windows)

Moved here from uservoice to @bitcrazed's request

@stereokai stereokai added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Sep 20, 2019
@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 Sep 20, 2019
@zadjii-msft
Copy link
Member

This sounds kinda like a commandline ask, but not necessarily a Terminal ask.

I don't think it's a bad idea, but it's also not necessarily home on this repo. However, I'm not sure there is a better home for this. This set of asks kinda fits with colortool if you ask me - things that improve the commandline experience on Windows that we track as a part of this repo.

@zadjii-msft zadjii-msft added Area-User Interface Issues pertaining to the user interface of the Console or Terminal Product-Cmd.exe The issue is related to the legacy command interpreter, CMD.exe. Product-Powershell Issues in the modern command interpreter, Powershell.exe. labels Sep 20, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Sep 20, 2019
@driver1998
Copy link

driver1998 commented Sep 21, 2019

This might be a good idea for powertoys, like new commandline tool / powershell module to show toast messages, manipulate windows or what not.

@stereokai
Copy link
Author

This might be a good idea for powertoys, like new commandline tool / powershell module to show toast messages, manipulate windows or what not.

That kind of misses the point. The strength of this feature set is to allow CLI tool/library developers to provide a richer experience to their users by integrating with engaging OS features.

@driver1998
Copy link

driver1998 commented Sep 23, 2019

That kind of misses the point. The strength of this feature set is to allow CLI tool/library developers to provide a richer experience to their users by integrating with engaging OS features.

Then I guess you can always call Windows APIs in said CLI tool/library, rundll32.exe can also be useful sometimes.
Although I know sometimes Windows APIs require you to have a Window, or worse, a UWP CoreWindow in order to work, that will be tricky in a CLI tool. It would be cool to remove these limitations for those APIs.
Or maybe a special VT sequence to define a toast/message box? Such thing can also be cross-platform.

@zadjii-msft
Copy link
Member

So as much as a VT sequence could work in this scenario, I think a separate standalone commandline application for sending a notification might be a better solution for at least the sending a notification bit here. That way, we wouldn't need to rely on the Windows Terminal handling that VT sequence - users using any terminal on Windows could still send notifications from the commandline by calling that standalone exe. That's my 2c on the matter at least.

@widersky
Copy link

widersky commented Sep 24, 2019

Would be nice if commands that are done in background (when other app is active and terminal works, e.g. on npm install) have notification like "npm command finished!".

@DHowett-MSFT DHowett-MSFT added this to the Terminal Backlog milestone Oct 29, 2019
@DHowett-MSFT DHowett-MSFT removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Oct 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-User Interface Issues pertaining to the user interface of the Console or Terminal Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Cmd.exe The issue is related to the legacy command interpreter, CMD.exe. Product-Powershell Issues in the modern command interpreter, Powershell.exe.
Projects
None yet
Development

No branches or pull requests

6 participants