Recent Posts
Around ‘n’ About
- SuperGenPass: Generate your passwords dynamically using a master password and the site domain. Handy and more secure than that password you currently use everywhere…
- Fro Knows Photo!: He does!
- Web Designers Checklist: Oodles of info on browser support for modern CSS & HTML features.
- Filler Item: Find that low price item that you need to qualify your Amazon.com order for free shipping.
- Unofficial Ruby Usage Guidelines: A pretty good overview of common sense ruby formatting and use. Good for Ruby n00bs like me ;)
Geek++
TheGipster on Flickr
WookieeBoy on Twitter
Shawn Parker on about.me
Shawn Parker on Zerply
css signature: top-frog-com

Great thanks a lot! Thats what I have just been lookin for!
This is fantastic! absolutely what I was looking for…;-D I really appreciate that you riddled this out.
cheers,
m!
Great solution. Works like a charm for me.
Thanks a lot!
super cool. thnx!
Thank you SO much… I’ve messed up my Coda install pretty good in the past when trying to fix this!
Thank you ! Great solution ! It work very well !
Thanks for this information. I know it was years ago now but my entire workflow begins and ends in coda so having bash syntax highlighting makes my life better.
This didn’t work for me even though I followed it to the letter. To say I was disappointed was an overstatement. Mildly annoyed… possibly but it seems CODA 2 > does not like this work around
Well, to be fair this article is almost 3 years old. When written SubEthaEdit and Coda shared the same version of the syntax highlighting engine.
Coda 2 appears to have moved to a newer version. I tried pulling in the bash mode from the current SubEthaEdit version and that, while it properly recognized bash files, it didn’t colorize anything.
I’ve long since abandoned hope on being productive in Coda and all my mental efforts are in TextMate and the JetBrains suite of products.