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

Allow extensions to create file based output channel #41672

Closed
sandy081 opened this issue Jan 16, 2018 · 6 comments
Closed

Allow extensions to create file based output channel #41672

sandy081 opened this issue Jan 16, 2018 · 6 comments
Assignees
Labels
api *out-of-scope Posted issue is not in scope of VS Code output Output channel system issues
Milestone

Comments

@sandy081
Copy link
Member

sandy081 commented Jan 16, 2018

Allow extensions to create an output channel based on a file. For example, if an extension is logging into a file and if the extension wants to show those logs in the output channel, this will help you create an output channel streaming from that log file.

@TomasHubelbauer
Copy link
Contributor

@sandy081 Can you clarify what this would actually allow the extension authors to do? Something like treating output channels as files where changes to the file would get reflected in the output channel contents (allowing us to rewrite already output content)?

@sandy081
Copy link
Member Author

sandy081 commented May 7, 2018

@TomasHubelbauer Updated the description.

@TomasHubelbauer
Copy link
Contributor

@sandy081 is it feasible for this to be developed by an external contributor? Is it easy enough? To me it sounds like a file system watcher on the file and some hooks the the Output channels APIs could do the job. If I'm correct, would you mind posting some pointers in the code the community could use to try and pick up this work?

@sandy081
Copy link
Member Author

@TomasHubelbauer Yes this is easy to implement. We already have file based output channels internally. This is only to expose it as an API.

Since it is an API we have some protocols to follow, we would need extension authors requiring for this feature with proper use cases. Since there are no real time requirements from extension authors, I would keep this on hold until we get some.

@sandy081 sandy081 modified the milestones: On Deck, Backlog May 15, 2018
@TomasHubelbauer
Copy link
Contributor

Please check out rust-lang/vscode-rust#306 (comment) for one possible use case.

@sandy081 sandy081 added the *out-of-scope Posted issue is not in scope of VS Code label Sep 12, 2018
@vscodebot
Copy link

vscodebot bot commented Sep 12, 2018

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

@vscodebot vscodebot bot closed this as completed Sep 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api *out-of-scope Posted issue is not in scope of VS Code output Output channel system issues
Projects
None yet
Development

No branches or pull requests

2 participants