Support for dynamic UTIs about qlmarkdown HOT 5 OPEN

I haven't looked into dynamic UTIs yet. Are you saying that I just add that to the .plist in the next release, or are dynamic UTIs something we have to look at supporting... dynamically?

from qlmarkdown.

Yeah, we can just add to the plist, and it'll work. According to the referenced article (and this Stack Overflow entry), dynamic UTIs are based on the file extension, so they won't change.

Submitting a pull request for this momentarily.

from qlmarkdown.

Cool. Thanks. I'll be happy to merge that in.

On Sun, May 25, 2014 at 8:21 PM, Craig Buchek [email protected]:

Yeah, we can just add to the plist, and it'll work. According to the
referenced article (and this Stack Overflow entryhttp://stackoverflow.com/questions/8003919/are-dynamic-utis-stable,
dynamic UTIs are based on the file extension, so they won't change.

Submitting a pull request for this momentarily.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/37#issuecomment-44151156
.

from qlmarkdown.

I wonder if this could fix #14...

from qlmarkdown.

@tarwich I don't think it'd help with #14. Because .txt is already registered, they'll always come up as the public.plain-text UTI.

I don't think there's a way to register a double extension like that, either.

from qlmarkdown.