Repository navigation
Conversation
…lves whomwah#87 So cheaply pretending to be a QLGenerator from Apple seems to be the way to make Quick Look use QLStephen also for UTIs with direct, indirect, explicit and implicit (for dynamic UTIs) conformance to UTI registered for it. If this is the fix, I can only remember that most used language in programming is profanity.
|
I tested this fix and it worked for me. Commands and sample output: /Users/mikael/Library/QuickLook/QLStephen.qlgenerator/Contents/Info.plist: Thank you Ivan. *** UPDATE *** |
Restores support for avi files and for less common codecs in .mov, .ts and .m2ts files. Fixes #86 #91 Inspired by whomwah/qlstephen#135
|
This is not working for some reason: `JimsMBPro:Packages jim$ git clone git@github.com:toy/qlstephen.git Please make sure you have the correct access rights |
|
@glorious1 Try |
|
@toy |
|
@glorious1 I failed with copy-pasting 🤦, see the corrected command |
|
I set up my github keys again and was able to get it with the original URL, thank you. Also thanks to @MikaelHashiCorp for putting in the build commands; I would have never guessed it requires Xcode and how to do it. After running these for good measure: it works like magic! Thank you @toy EDIT: I found a few text files that didn't work, like xml, srt. I just used mdls to get their kMDItemContentType, like "public.xml" and "dyn.ah62d4um4ge81g6xy", and added them and "public.item" also to |
|
This works! So many file extensions are working again. 🥲 Thank you, @toy! On macOS 14.2.1, with Xcode 15.1, my first build failed with a warning about MACOSX_DEPLOYMENT_TARGET. So I opened the project in Xcode and set a Deployment Target. Then I ran |
|
Does this still work for Sequoia? |
Mah, I tried to follow the instructions but couldn't manage to get this working with Sequoia. I hugely miss its functionality. |
|
@fvaccari if you want your functionality back (and then some): https://github.com/j-256/qlomni |
|
Hi James,
thanks for pointing me to qlomni. I’ll go reading the docs and see how I can customize it to fit my needs. I’ve plenty of extensions to deal with, generated by a suite of Fortran programs that is of no interest for people not using them. So no point to make a request for including those extensions in the standard qlomni release.
My hope is to have a user-friendly way of customizing the set of considered extensions
… On 30 May 2026, at 05:53, James ***@***.***> wrote:
j-256 left a comment (whomwah/qlstephen#135)
@fvaccari if you want your functionality back (and then some): https://github.com/j-256/qlomni
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Understood, thanks!
… On 30 May 2026, at 20:41, James ***@***.***> wrote:
j-256 left a comment (whomwah/qlstephen#135)
@fvaccari ask and ye shall receive. Unfortunately it's impossible to have the list be dynamic at runtime, so you need to build from source, which requires Xcode.app.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you were mentioned.Message ID: ***@***.***>
|

So cheaply pretending to be a QLGenerator from Apple seems to be the way to make Quick Look use QLStephen also for UTIs with direct, indirect, explicit and implicit (for dynamic UTIs) conformance to UTI registered for it.
If this is the fix, I can only remember that most used language in programming is profanity.