add user-defined file-ext but supported format for "File Explorer add-ons utility"

[runck]

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!

[Jay-o-Way]

What is/are the extension(s) you would like to see?
Check out issue #1527, it's being worked on right now. Maybe that'll add the things you want.

[runck]

Yes, very similar with maybe a little difference.
Actually I sometimes create my own extension(s) for special softwares, which is not common. So it is greater if there is a way to tell the powertoy that, this or that unknow extension is just a plain txt or other supported format.
I am not sure, but this issue could be closed, if it is the same thing with the mentioned issue from developers' views.
Thank agian.

[crutkas]

#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 foo, treat it like bar ext

[crutkas]

This then would solve #6019 and #9109 since you'd proxy them against Markdown

[crutkas]

Issue #10126 needs to be done as part of #1527 / this item.

[runck]

Yes as you said, I think my problem can be solved if with the proxy style.

[Pindar777]

Hi @crutkas,

is there any news concerning the implementation of the proxy style solution which would also solve #9109?

Cheers

[crutkas]

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

[crutkas]

If this is something you feel strongly on and would like to help out with, please lets chat!

[Korb]

Check out issue #1527, it's being worked on right now

Not anymore.

This then would solve #6019 and #9109 since you'd proxy them against Markdown

Issue #10126 needs to be done as part of #1527 this item.

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.

[koosvanderkolk]

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.