Activate the function "Do not save commands" #7907

Closed
opened 2026-01-31 01:15:32 +00:00 by claunia · 4 comments
Owner

Originally created by @Aylexx on GitHub (May 3, 2020).

Description of the new feature/enhancement

This function should delete the executed commands or overwrite them after a restart or with another text.

Proposed technical implementation details (optional)

1. Terminals sends typed char
2. PowerShell receive typed char
3. Terminal displays chars

grafik

Originally created by @Aylexx on GitHub (May 3, 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! --> # Description of the new feature/enhancement This function should delete the executed commands or overwrite them after a restart or with another text. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) **1. Terminals sends typed char 2. PowerShell receive typed char 3. Terminal displays chars** ![grafik](https://user-images.githubusercontent.com/64732227/80913440-ec4d4180-8d44-11ea-98e2-5ebe798283bc.png) <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 01:15:32 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (May 3, 2020):

You have read the issue from which you copied this text. There is no reason for you to file a second one.

@DHowett-MSFT commented on GitHub (May 3, 2020): You have read the issue from which you copied this text. There is no reason for you to file a second one.
Author
Owner

@Aylexx commented on GitHub (May 3, 2020):

Which issue do you mean?
@DHowett-MSFT

@Aylexx commented on GitHub (May 3, 2020): Which issue do you mean? @DHowett-MSFT
Author
Owner

@DHowett-MSFT commented on GitHub (May 3, 2020):

Sorry, there's a lively discussion in #5378 -- people are asserting that it is possible, but nobody can tell me how. 😄

The user who filed that issue has a lot of friends coming over to this repository to keep filing the same requests, and it looked like some of the text in this issue was copied from there, so I thought that it was a clone. It turns out that it isn't (sorry!), but the issue is still a /dupe of #5378.

More information on why it may not be possible in this comment: https://github.com/microsoft/terminal/issues/5378#issuecomment-616883348

@DHowett-MSFT commented on GitHub (May 3, 2020): Sorry, there's a lively discussion in #5378 -- people are asserting that it is _possible_, but nobody can tell me how. :smile: The user who filed that issue has a lot of _friends_ coming over to this repository to keep filing the same requests, and it looked like some of the text in this issue was copied from there, so I thought that it was a clone. It turns out that it isn't (sorry!), but the issue is still a /dupe of #5378. More information on why it may not be possible in this comment: https://github.com/microsoft/terminal/issues/5378#issuecomment-616883348
Author
Owner

@ghost commented on GitHub (May 3, 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 3, 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#7907