Private Mode in Terminal 🧐 #7490

Closed
opened 2026-01-31 01:05:14 +00:00 by claunia · 4 comments
Owner

Originally created by @aloamaloa on GitHub (Apr 19, 2020).

Description of the new feature/enhancement

Private mode in the terminal as with the browsers? :D

Proposed technical implementation details (optional)

Originally created by @aloamaloa on GitHub (Apr 19, 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 Private mode in the terminal as with the browsers? :D <!-- 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) <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 01:05:14 +00:00
Author
Owner

@aloamaloa commented on GitHub (Apr 19, 2020):

I mean that would be fantastic! 👍 💯

@aloamaloa commented on GitHub (Apr 19, 2020): I mean that would be fantastic! 👍 💯
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 19, 2020):

You seem to be affiliated with @Qantex, and you therefore must know that he filed an issue for this already. /dup #5378

@DHowett-MSFT commented on GitHub (Apr 19, 2020): You seem to be affiliated with @Qantex, and you therefore must know that he filed an issue for this already. /dup #5378
Author
Owner

@ghost commented on GitHub (Apr 19, 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 (Apr 19, 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!
Author
Owner

@ghost commented on GitHub (Apr 19, 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 (Apr 19, 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#7490