Closed taw123 closed 2 years ago
Hi, the problem is that in your system the .config
files are linked to the UTI com.macromates.textmate.config-file
which I don't currently handle.
Before releasing a new version I ask you to try the one I am attaching here to check if it works in your system.
To run it, replace the old version with this one and ctrl click on the icon and from the menu choose open and authorize the execution.
The application has perhaps grown in a somewhat messy way, developed a little for fun, and needs to be updated from a graphical and usability point of view.
I never even considered the accessibility aspect. Maybe you could tell me which symbology to use to report Support & Handled vs Potentially supported formats. (For now there is the tooltip for the icon status).
Success !! (though I of course did end up having to kick qlmanage (first -m then -r), followed by restarting the Finder before QL found the new build.
While I was never an HI Engineer, sometimes even non-artists can be artistic... What was used for server Admin (since the pricked colors that were of equal brightness and saturation- a real sore spot for those with selective color vision), was a option to show each of the status indicators as shapes (circle=good/green, triangle=warning/yellow and square=error/stopped/red)... I only offer that as a suggestion to start the thought process.
Another approach you can also see from the original Aqua window controls (what we call "gumdrops"), take on a secondary UI when the mouse hovers over (long before Windows have "tooltips").
I hadn't realized you did this untill you mentioned (guess I was a bit to impatient when I originally tried hovering over the indicator, and thus sent the message about color accessibility. head smack
One quick passing question I also noticed the MD files are not being processed by Syntax
I didn't look to see if this is another case of Xcode or the OS taking precedence over everything else but thought I would mention it in passing in case it's a common question...
All the best and hanks again for the speedy response, and fix ! If ever I can help let me know... --T
Generally for the new plugin to be recognized it is necessary to delete the old version (and also delete it from the recycle bin) and launch the new one. If it does not work in the system preferences / extensions / quicklook, the extension must be disabled and re-enabled.
qlmanage
I doubt has any use for quicklook extensions (it is meant to work with thw qlgenerators thah uses the old deprecated api).
Markdown files are purposely unsupported as it would show syntax highlighting and not formatted text as most people would like.
For the markdown files I have however developed a special plugin (which if desired can be set to display the syntax instead of the formatting): QLMarkdown.
While I did move the brew'd app (actually the link to the trash) and installed the link you provided (as well as refreshing/re-enabling System Preferences/QL), I didn't likely empty the trash as you mentioned... so perhaps that was why I had to relaunch the finder. Regardless as I said no worries.... And I've now added QLMarkdown to my arsenal! 👍
Given I think you pushed this change to release as 2.1.10 (59). I'm going to close this issue. Thanks again for everything.
First as someone who over the years has used a number of solutions BEFORE your creation(re-creation) I am quite impressed. I have used it for years and thank you for all the effort as a user and as a former former Evangelist at Apple in Dev Relations for MANY years!
Unfortunately the question. Though having used for a while and works for almost all files I would expect, I and a bug or much more likely I perhaps don't understand the internals and configuration as well as I suppose I should (or just a stupid error- happens to us all)...
I have a standard install of Syntax (close to current- 2.1.9) running on Catalina 10.15.7.
For some reason text based .config files are not being parsed by the QL extension inspire of my assumption that should be supported given the current readme.
Any thoughts? I would have thought if isn't were part of the standard support configuration that II would just need to add the UTI for my non loading file to your config (somehow) & add .config extension to the current ini profile (or whatever you call the config set for ini parsing)...
Thanks for any help you can offer.....
Configuration data below....
Sample file is confirmed to be pure txt
File is NOT handled by Syntax:
Screenshot of QL for testing file, NOT showing Syntax parsing:
Metadata query for the test file:
Syntax Inquiry command of the file shows 3 potential associated UTI: (screenshot attached) Unfortunately I can't distinguish the color indicator you chose to to show Support & Handled vs Potentially supported but not handled (btw I worked for years to make sure the Apple HI Team always included color-blind/alternate color indicators... (long before accessibility became a thing, which is one reason the server manager UI allowed for a display with color or shapes) But I digress....
QL dump of Syntax: (showing that org.sbarex.conf, com.macromates.textmate.scheme, com.macromates.textmate.standard-ml are all supported but no listing for com.coderunnerapp)