-
Notifications
You must be signed in to change notification settings - Fork 49
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
Not working for .sql files #65
Comments
Can you provide me an SQL file that is not working, please? I can't reproduce locally the problem. |
For TXT, it's not a bug but a feature ;-) (see #48, I removed the TXT file support in favor of QLStephen). For ASP, can you provide me a file, please ? |
Sorry for the late reply... Inside this zip file, there are 2 files: sample.asp, and sample.sql Please, take a look at the following screenshot: As you can see, there's a reason for .asp files not use QLColorCode... :-) I'm just not sure how to "fix" it... Does it have anything to do with editing the Info.plist file? (as described in the README.md) If so, is this the same procedure I have to do in order to make .txt files use QLColorCode as well? And then there's the .sql files that still make me wonder what's going on... If you need further details, please let me know. Thank you so much for your time. |
Hi again. I kind of "fixed" everything but .sql files to my liking... I just edited Info.plist adding these lines inside the LSItemContentTypes array: <string>public.plain-text</string>
<string>public.data</string>
<string>public.content</string> And then I uninstalled QLStephen, 'cause these edits made QLColorCode render everything that QLStephen would, so I don't need it anymore... :-) The only files that are still "broken": .sql Any news on this? Thanks again. |
Hi.
Since last update (done via Homebrew), .sql files don't work properly with QLColorCode anymore.
Maybe it's because of Highlight being also updated, but I'm not able to tell where the problem really is.
Any help will be greatly appreciated.
Thanks.
Cristiano
The text was updated successfully, but these errors were encountered: