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 ability to save console scroll buffer to a file. #3584

Closed
swpalmer opened this issue Nov 14, 2019 · 2 comments
Closed

Add ability to save console scroll buffer to a file. #3584

swpalmer opened this issue Nov 14, 2019 · 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

@swpalmer
Copy link

Description of the new feature/enhancement

Add the ability to save the scroll buffer to a file so it can be easily searched and large regions can be copied and pasted.

Proposed technical implementation details (optional)

You have the buffer... adding a context menu to the tab to save the history shouldn't be to hard.

@swpalmer swpalmer added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Nov 14, 2019
@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 Nov 14, 2019
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This looks like it's actually something that's already been suggested, so I'll direct discussion to that thread.

/dup #642

Thanks!

@ghost
Copy link

ghost commented Nov 14, 2019

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 Nov 14, 2019
@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 Nov 14, 2019
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