MacOS – Finder Enhancement – Customize Icon for filetype

You could make new CFBundleDocumentTypes entries in /Applications/TextWrangler.app/Contents/Info.plist. Many extensions are currently defined under a single entry with the CFBundleTypeName TextWrangler text document:

<key>CFBundleDocumentTypes</key>
<array>
    <dict>
        <key>CFBundleTypeExtensions</key>
        <array>
            <string>a</string>
            <string>as</string>
            <string>asm</string>
            <string>asp</string>
            <string>bashrc</string>
            <string>c</string>
            <string>c++</string>
            <string>cc</string>
            <string>cfm</string>
            <string>conf</string>
            <string>cp</string>
            <string>cpp</string>
            <string>cshrc</string>
            <string>css</string>
            <string>cxx</string>
            <string>equ</string>
            <string>erb</string>
            <string>f</string>
            <string>f77</string>
            <string>for</string>
            <string>ftn</string>
            <string>h</string>
            <string>h++</string>
            <string>hpp</string>
            <string>htm</string>
            <string>html</string>
            <string>inc</string>
            <string>j</string>
            <string>java</string>
            <string>js</string>
            <string>json</string>
            <string>jsp</string>
            <string>log</string>
            <string>m</string>
            <string>mm</string>
            <string>p</string>
            <string>pas</string>
            <string>pch</string>
            <string>pch++</string>
            <string>php</string>
            <string>php3</string>
            <string>pl</string>
            <string>plist</string>
            <string>plx</string>
            <string>pm</string>
            <string>ppu</string>
            <string>profile</string>
            <string>r</string>
            <string>rb</string>
            <string>rez</string>
            <string>rhtml</string>
            <string>rss</string>
            <string>s</string>
            <string>sql</string>
            <string>shtm</string>
            <string>shtml</string>
            <string>tcl</string>
            <string>tcshrc</string>
            <string>text</string>
            <string>txt</string>
            <string>wml</string>
            <string>xhtml</string>
            <string>xml</string>
            <string>xsl</string>
            <string>xslt</string>
            <string>yaml</string>
        </array>
        <key>CFBundleTypeIconFile</key>
        <string>TextWranglerTextDoc.icns</string>
        <key>CFBundleTypeName</key>
        <string>TextWrangler text document</string>
        <key>CFBundleTypeOSTypes</key>
        <array>
            <string>TEXT</string>
        </array>
        <key>CFBundleTypeRole</key>
        <string>Editor</string>
    </dict>

As usual, making changes inside the bundle invalidates the code signature. A new certificate can be assigned with codesign -f -s - /Applications/TextWrangler.app.

Column previews in Finder are in fact provided by QuickLook, not Preview – as are the icons displaying the file contents, the CoverFlow icons and the QuickLook preview proper you invoke by pressing Space or Cmd+Y on a selected file.

QuickLook uses plugins to display file contents – a piece of code rendering the file contents and telling the QuickLook server it can do so (see the QuickLook Programming Guide if you want the technical details). You need plugins because files can be binary data – without knowledge of its structure, no representation of the file is possible – or textual data that needs processing – HTML for instance, which you’ll probably prefer to preview rendered, not as raw source. They also must be limited to specific, known file types (to be precise: Uniform Type Identifiers, or UTIs for short) for this exact reason – a rendering plugin for HTML will not give you a usable preview for a JPEG. OS X provides quite an impressive default collection of these plugins (located in /System/Library/QuickLook), and applications you install add their own (located in the application package itself, /Library/QuickLook or ~/Library/QuickLook). You can also add some yourself to those two last locations.

In the case of text files without an extension, the problem is OS X’s built-in plain-text QuickLook plugin is not assigned to these as they do not correspond to a UTI it handles. However, there is a 3rd party QuickLook plugin adding that functionality: QLStephen. Just download it and install it according to its installation instructions on GitHub and you should be good to go.