relikd

could it be that a color profile is attached to the image?

@nicolas-renard It is a shot in the dark, but can you try this please: replace line 53 in `Sublime Text 3/Packages/Anaconda/anaconda_server/handlers/jedi_handler.py` ```python jedi_project._environment_path = self.settings.get("python_interpreter") ``` with: ```python os.environ.setdefault('VIRTUAL_ENV', self.settings.get("python_interpreter"))...

Your description of the problem ("does not work after a sublime restart") sounds a lot like #878 Try setting the full python path in Anaconda user settings: `"python_interpreter": "/usr/bin/python"`

Thanks for the PrivateLogs link. Yep, I encountered this issue too. Even pre Catalina, in fact even pre Mojave. Just recently I was working on QLOPML on a 10.13 machine....

Do you happen to know which of them might be the generic QL plugin? The best I got is `/System/Library/QuickLook/Text.qlgenerator`, which conforms to: ``` public.plain-text public.rtf com.apple.rtfd org.oasis-open.opendocument.text com.apple.property-list public.xml...

Also, I tried creating a custom `dyn.*` adopting the `public.data` UTI without any extension. But that didn't work either. Setting the extension to `*` or nothing at all, also didn't...

Can you uninstall the brew and try again with https://github.com/whomwah/qlstephen/releases/latest (following the `xattr -cr` procedure). Maybe something was messed up in the brew installation. I have a working† qlstephen on...

seems very strange for a plain text file to be executable. Can you create a new empty file with just "hello world" and save that as `LICENSE`. Also, try `chmod...

I think executable files were never supported by QLStephen. `.sh` will display, though that might be an apple ql plugin in action, haven't verified. The problem with executable files is...

I've created PR #94 just in case. If we dont want it or there are unforeseen side effects, just say so and I'll delete my fork ;-)