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: Logging Input and Output for Each Terminal Tab Automatically #18384

Closed
lededev opened this issue Jan 2, 2025 · 3 comments
Closed
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@lededev
Copy link

lededev commented Jan 2, 2025

Description: I would like to request a feature that allows logging of input and output for each terminal tab in Windows Terminal automatically (Not export text manually, Because I often remember to review the terminal output only after I close the tab or the entire terminal program). This feature would be similar to the logging functionality available in mintty, where logs can be configured in the configuration file (e.g., ~/.minttyrc with Log=/var/log/mintty/%Y%m%d@%H:%M:%S_log%d.txt).

Use Case: This feature would be extremely useful for users who need to keep a record of their terminal sessions for auditing, debugging, or documentation purposes. It would be beneficial for various types of terminals, including PowerShell, CMD, WSL, and MSYS2.

Proposed Solution: Implement a logging feature that can be configured in the Windows Terminal settings, allowing users to specify the log file path and format. The logs should include both input and output for each terminal tab.

Additional Context: Currently, users have to rely on external tools and scripts to achieve this functionality. Having this feature built into Windows Terminal would greatly enhance its usability and convenience.

@microsoft-github-policy-service microsoft-github-policy-service bot 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 Jan 2, 2025
@lededev lededev changed the title Howto export text by default every session, or we say as log file Feature Request: Logging Input and Output for Each Terminal Tab Jan 2, 2025
@lededev lededev changed the title Feature Request: Logging Input and Output for Each Terminal Tab Feature Request: Logging Input and Output for Each Terminal Tab Automatically Jan 2, 2025
@83nf15h
Copy link

83nf15h commented Mar 1, 2025

#14018 and #9700 are looking for a similar feature but have had no progress in a long time. Would be great to have this included.

@zadjii-msft
Copy link
Member

Yep, those are definitely the right dupes. Thanks!

/dup #14018

Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot 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 Mar 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

3 participants