-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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 user-defined file-ext but supported format for "File Explorer add-ons utility" #10425
Comments
What is/are the extension(s) you would like to see? |
Yes, very similar with maybe a little difference. |
#1527 is only known formats. You can't make "unknown" act like text, what is the file is some massive binary file, then you're encoding and displaying. How i'd imagine this would work would be proxy style. When you see ext |
Yes as you said, I think my problem can be solved if with the proxy style. |
It isn't something currently on the roadmap for the near future. https://github.com/microsoft/PowerToys/wiki/Roadmap The monaco engine support is the next big file explorer item we'd be adding in but has installer and settings work that needs to be done in the 0.51 iteration |
If this is something you feel strongly on and would like to help out with, please lets chat! |
Not anymore.
All of the above were closed without a decision to add support for many extensions that are actually plain text. It remains for me to vote for this proposal, as the only one that has not yet been closed. |
This would be a great improvement. E.g. we have .module files which are in fact .php files. It would be very nice if we could map these extensions somehow. |
Thanks to this power tool, I love the function named "Preview Pane" in "File Explorer add-ons utility", which supports markdown format.
However, some of my other markdown tools use different file-ext than simply .md or .markdown. Therefore, it would be great if there is an option to add user-defined file-ext, mapping to the supported format when previewed.
Thanks!
The text was updated successfully, but these errors were encountered: