-
Notifications
You must be signed in to change notification settings - Fork 2
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
Don't get a proper QuickLook preview, just a window with DEBUG as a header #2
Comments
Seeing this for PNGs, JPEGs, any sort of file I'd normally get a preview with in Finder. |
Thank you for the kind words! You're right, I am experiencing this as well. I suspect it's a problem with High Sierra. Let me check and get back to you. |
Should be fixed. Can you re-install the plugin and let me know if it works for you now? |
@mherrmann Works now! Fantastic. Definitely not regretting buying that license earlier today now. Great work, excited to see how fman progresses! |
Glad to hear it! Thank you very much for getting a license. I really appreciate it. fman is just getting started ;) |
Awesome, just saw it on HackerNews last week I think, and was out sick for a few days and finally getting around to playing around. Works almost exactly with how I imagine/use the file system, so very excited to see it grow. |
Cool :) If you find there is something that needs to be improved, just let me know. |
I'm getting this same issue on Sierra, but it's opening in a separate app (qlmanage) |
@mwean could you post a screenshot? |
@mwean do you get the same when you type
? Also, does it happen for all files? Eg., have you tried for images? |
Yeah, it seems the same if I use that command. It seems to work better for images, but it still shows the qlmanage icon in the dock and the window has "[DEBUG]" in the name. I also got this when I ran the command:
So it's possible there's other stuff going on. |
Interesting, thanks Matt. Does it work when you do
? |
That seems to work better (in that it pops up right away), but I still get those error messages, and it still says "[DEBUG]" |
So you're seeing the correct contents inside the Preview window then? The "[DEBUG]" is ugly but the error message don't matter too much I think, because you wouldn't see them when launching the feature from fman. |
Sorry, yes I see the correct content with sudo, not in fman |
If I recall correctly, it's somehow possible to write plugins for QuickLook. Do you happen to know of a plugin that might be installed on your system - and may require the elevated permissions? |
Yeah, I definitely have plugins, but they all work fine in other apps like PathFinder and ForkLift. Are you invoking quicklook in a different way? |
No, I'm doing exactly |
No, I'm saying are you doing something different than other Mac apps |
I don't know how the other apps do it, so I can't really answer that question unfortunately. One thing that's special about fman is that it is a cross-platform Qt app, rather than a native one. I'm just trying to "hack" the other apps to see how they're doing it. |
I hate to reopen a closed ticket, but this is definitely still an issue, and a big one for me. It's the biggest barrier to me using fman exclusively. My typical use for a file browser is to quickly traverse folders and get a quick glimpse at the contents of the files in them. Having to open them in an app steals keyboard focus and defeats the purpose of fman. It works fine for some file types, but hangs one others. It seems to work fine on .sh .config and files with no extension. It hangs on .html, .php, .py, any image/video files, and hangs very badly on .json files. You asked previously about QuickLook extensions so I'll point you to this repo https://github.com/sindresorhus/quick-look-plugins I have several of these installed and they work fine, even when I'm using preview via fman. I've tried uninstalling all of them and still have the same issues. Hope this is helpful. I'd love to get this working correctly. |
Loving fman so far, just installed this plugin, but not getting any luck with QuickLook. Every time I try to use it, I get the following:
The text was updated successfully, but these errors were encountered: