Add Clear the previous output shortcut action #8204

Closed
opened 2026-01-31 01:23:19 +00:00 by claunia · 2 comments
Owner

Originally created by @3axap4eHko on GitHub (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

Originally created by @3axap4eHko on GitHub (May 17, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # 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
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 01:23:19 +00:00
Author
Owner

@DHowett commented on GitHub (May 17, 2020):

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

@DHowett commented on GitHub (May 17, 2020): Thanks for the request! This is a /dupe of #1882, which requires #1193
Author
Owner

@ghost commented on GitHub (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 commented on GitHub (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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8204