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

Add Clear the previous output shortcut action #5954

Closed
3axap4eHko opened this issue May 17, 2020 · 2 comments
Closed

Add Clear the previous output shortcut action #5954

3axap4eHko opened this issue May 17, 2020 · 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

@3axap4eHko
Copy link

3axap4eHko commented May 17, 2020

Clear the previous output shortcut action

Different terminals use different commands to clear output: cls, Clear-Host, clear and etc.
It would be great to clear the previous output by the same hotkey at any terminal.
Currently Ctrl+K does not work properly

@3axap4eHko 3axap4eHko added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label May 17, 2020
@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 May 17, 2020
@DHowett
Copy link
Member

DHowett commented May 17, 2020

Thanks for the request! This is a /dupe of #1882, which requires #1193

@ghost
Copy link

ghost commented May 17, 2020

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 May 17, 2020
@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 May 17, 2020
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