please add support for .jsp file it will be a great help

thanx

I would like an option for wrapping long lines to the QL window border, preferably for certain languages. For example, wrapping .tex files but not .cpp....

If there isn't a support for changing tab sizes (at least I haven't found it yet), please add it, the tabs are far to big for me.

and thanks for making a great plugin :)

@tigaenamb: Please see the FAQ and file a bug on .jsp if you want to help me add support.

I should clarify that language requests should definitely be filed as issues, not listed here. I'll put something to that effect at the top of the page

As for the others, it would be nice to have a configuration mechanism other than "edit the colorize.sh file". This has been on my TODO list for a while. I'll file an issue to remind myself.

great plugin! any way to get it to handle files without extensions? things like "Makefile", "Readme" etc of type Plain text just show up with with the generic document icon.

cheers phil

Is there any way to force OS managed QL Source files to be handled by QLColorCode? It looks nicer, especially now that I can change preferences.

@pkpowell: I haven't set QLCC to handle plain text since that's not really its mission, but I might reconsider that decision.

@elventear: The process by which the OS decides which plugin to use for a given file type is not well documented. One thing you can try is to run qlmanage -p somefile.foo 2>&1 | grep 'generator used' and look at the output that gets produced. You'll see something like:

2008-01-07 13:50:57.476 qlmanage[56917:5f03] [QL] Previewing /Users/n8gray/src/flickr/Notes.txt. Content type UTI: public.plain-text. Generator used: <QLGenerator /System/Library/Frameworks/QuickLook.framework/Resources/Generators/Text.qlgenerator>

That tells you what content type the OS thinks the file is and what generator was used to handle it. If you really want QLCC to handle that file, you can add the content type UTI (in this case public.plain-text) to QLCC's Info.plist file in the LSItemContentTypes array.

Oops! That should be grep 'Generator used', not grep 'generator used' (capital G)

@n8gray for the BIG help

i havent found any bug yet but i'll inform later if exist

Can you add a support for .asp file it will be a great help

thanks

it display 2-byte characters as broken. do you have a plan to support this problem?

thanks. :)

I would love to see perl syntax support. Highlight seems to have support for it. I am sure you know this but the extensions are .pl and .pm

Cheers Joe

I just saw your post asking not to ask for new language support here . . . Sorry. I would be willing to help to add the perl support. How can this be done?

Yes please it would be great if it could handle plain text. Also usefull for all unix shell script without extension. Maybe with a way to easily activate it for people who need it ? If you dont plan to add this feature, can you explain (for example in the FAQ or here) how we could activate/desactivate it ourself ? Thank you for all :)

@deepscarmac: See issue 12 in the issue tracker. I'm aware of the problem but I'm not sure how to solve it. I do intend to fix it.

@joeworkman: Perl already has a UTI defined by the OS (public.perl-script) so it should already work with QLCC. In my testing it does work.

@jlgr...: I would love to have it work for scripts without extensions but AFAIK there's no way to do it. I haven't planned to have QLCC handle plain text but I'm considering changing my mind on that. You can add public.plain-text to the LSItemContentTypes array in the Info.plist file if you want to enable it.

My vote goes to out of the box support of public.plain-text, because Apple's plain text generator needs to be pointed out to encoding of text by adding an extended attribute to file:

http://vnoel.wordpress.com/2008/06/18/weird-utf-8-bug-in-quicklook-its-the-ea/

QLColorCode could fix this.

Hi. I'm also voting strongly for plaintext support so that all those files without suffixes can be read at a glance. Something that Apple should have done but it may be that it's left up to a product like this?

Please please add plaintext, .txt support - apart from enabling us to look at extensionless files of type plain text, it would also be a relief to quicklook .txt files in the larger font provided by your plugin.

Line numbers on the left of the preview box would make a lot of sense for a source code viewer!

I have created a QL plugin for plain text if anyone's interested:

http://whomwah.com/2008/11/27/quicklookstephen/

D

Ponies!

bash and sql are great, thanks! A nice addition would be groovy. (.groovy, .script) someone mentioned this too .jsp Thanks.

Thank you for this great pluggin. Please add support to MXML one day, that would be superb !

Add php support: http://pasteninja.com/paste/2306 (code via @ramsey on twitter)

Two things that would make this great plugin even more great:

- Custom style sheets, with or without a built-in editor - Support for .NFO files, particularly if it can properly display the text encoding as MS-DOS Codepage 437.

Proper support for markup languages like textile, markdown, ... would be nice. Right now I use

http://pypi.python.org/pypi/textile

and changed the colorize.sh accordingly

	*.textile )
		lang=html 
		reader=(/usr/bin/python /Users/Shared/Local/textile-2.x/textile.py $target
		)
		;;

to convert textile files on the fly. It does has some kinks but it suffices for now.

Re. files without extension ("Makefile", "Readme", etc.):

It is possible to enable QLColorCode to handle these files by editing Info.plist (using Property List Editor) and adding a type "public.data" to the list of "Document Content Type UTIs".

Of course then all extension-less types will be handled by QLColorCode, which might or might not be what you want...

Is it possible to implement IDL color syntax? I see it is supported by Highlight

Hi,

First thanks you for you software ! It's just great but it could be better... :P It is possible to enable QLColorCode to handle Makefile ?

thx

It's will help a lot

Support for XSL files (same as XML).

+1 for XSL support.

jspx and jspf would be nice

I hope I'm not asking something already here. I read thru the Readme, FAQ and as much of this as I could bear.

While you do describe how to add new types, it would be nice if there were instructions on how to just add extensions to common types like XML. For example, any app that uses Xml to store their settings but sets a different file ext. Or even .cfg, .conf or .pref are often xml files.

I did figure out how to do this but I had to poke at it a bit. For those of us with less time, it would be nice if the instructions were right in the ReadMe or the FAQ but not part of "how to create a new type". Very simple instructions like this:

If you want to add file extensions to the XML type, do this:

1. Add your extensions to the type ??? in Info.plist in the array under the "<key>public.filename-extension</key>" line.
2. Modify filetypes.conf by adding the file extensions you wish to the "$ext(xml)" line
3. Move the package out of the QuickLook?? dir and copy it back in
4. Log off or reboot

I was not sure but I also edited the ext/highlight/filetypes.conf

Adding formatting to XML would be awesome. Most of my XML documents are one liners.

add selection of text

64bit version for Lion, plz

Support for JSON files. 64bit version for Lion.

Support for JSON files. 64bit version for Lion.

Support for CoffeeScript?

The 2-byte texts of the UTF-16 plain text file were display as broken. please support it !!

Please add support for LESS & CoffeeScript? :)

I second @Andrius to add the ability to select and copy text.

One of the main reasons a do a "quick look" is to find some tidbit of info currently escaping me. When I find it my natural inclination would be to copy and paste it where I need it.

I think this feature would be a big boost to the usefulness of this excellent tool!

I have tried using the scattered bits of information about how to add other extensions to this tool without success. I may not be doing it right - but it is extremely difficult to understand exactly what needs to be done.

For example .xml files work great but .xsl or .xslt files do not show anything but a big fat document icon and text telling me thst it is an XSL Stylesheet.

Would you be kind enough to do a simple wiki page describing how to add other extensions?

Holding my breath ;-)

Thanks!!!