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

File Explorer lets the user indicate which file extensions should be previewed as txt #7255

Closed
IvoMerchiers opened this issue Oct 13, 2020 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@IvoMerchiers
Copy link

IvoMerchiers commented Oct 13, 2020

Summary of the new feature/enhancement

I often encounter files for which it would be very useful if they were rendered as .txt, even if their file extension is different. For example config (.conf), environment (.env) or other data structures such as .yml.

It would be very nice if I could define a list of file extensions that should be previewed as .txt. Some good default options might also be beneficial.

Some of these data structures would benefit from a dedicated implementation, but lacking that, just rendering the text would already be very helpful.


If you'd like to see this feature implemented, add a 👍 reaction to this post.

@ghost ghost added the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Oct 13, 2020
@crutkas
Copy link
Member

crutkas commented Oct 13, 2020

I think for most of the files you outlined, the Monaco render idea would solve it. #1527

@crutkas
Copy link
Member

crutkas commented Oct 13, 2020

we could have a settings page that then would handle this scenario. make .conf files render as json or something ....

@crutkas crutkas added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Oct 13, 2020
@crutkas crutkas closed this as completed Oct 13, 2020
@crutkas crutkas removed the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Oct 13, 2020
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

2 participants