Highlight error messages in syslog can be annoying

[GoogleCodeExporter]

From wolf.mcewen:

"""
Files in ~/Library/Logs/ (usually) have the extension ".log". Those can be 
displayed by Leopard 
directly, no additional plugin needed. As soon as QLCC is installed, it takes 
over - or at least is 
given the file to display (as seen with qlmanage -p). As highlight has no idea 
about logs (what a 
shame) is coughs up an error in the system log. And that is annoying to the 
max, if you happen to 
have 500 log files and screenfulls of error messages in the console log.
"""

Original issue reported on code.google.com by n8gray@gmail.com on 21 Nov 2009 at 6:29

[GoogleCodeExporter]

You originally asked how to disable QLCC for the com.apple.log UTI, but that's 
actually pretty tricky.  Apple 
doesn't provide a way to *exclude* a UTI that conforms to one you've registered 
for.

Disabling the Highlight error message, on the other hand, should be pretty 
easy.  I've sent an e-mail to André-
Simon about it.  In the meantime you can add the text "2>> /dev/null " (without 
the quotes) to each line in 
colorize.sh that starts with $reader.  (should be lines 95, 97, and 99)

Original comment by n8gray@gmail.com on 21 Nov 2009 at 6:44

[GoogleCodeExporter]

Thanks for answering! Sorry to be late to give thanks - been away. It might 
look as if I hadn't been interested 
- not at all! :-)

As a workaround I had added filetypes of which I knew to be text-only (log, 
conf, inf, ...) to the 
.../QLColorCode.qlgenerator/Contents/Resources/override/config/filetypes.conf 
as an extension of "verilog". 
That way QLColorCode *did* interpret those files (sometime with colorful 
results) and didn't barf.

That was obiously not the correct way to do things, so I sat down and edited 
TextEdit.app/Contents/Info.plist 
and added the UTIs for log, conf, inf etc. there.
Now Leopard is displaying those file with the build-in QuickLook-plugin ad 
leaves those of which it has no 
idea to QLColorCode, which does an extra-great job with it! And no errors in 
the console(.app). :-)

Life is good.

Thanks for being kind and helping me out!

As somebody on this planet might have the same problem, I've included my 
TextEdit.app-Info.plist as a 
crude example of where to extend TextEdit.

Original comment by wolf.mce...@gmail.com on 6 Dec 2009 at 8:27

Attachments:

• Info.plist