Jangro.com Social Media, Affiliate Marketing, etc. Heavy on the etc.

If you're new here, please subscribe to my RSS feed. And follow me on twitter. Thanks for visiting!

If you haven’t checked out Coda, it’s a beautifully designed and useful (looking) web development tool for OS X. If you do web development, you have your arsenal of tools… text editor, FTP program, terminal application, source code revision management.

Coda does it all in one window. Pretty sweet.

Maybe I’m just in love with their website, which is just a joy to use.

For years, we’ve used Cyberduck to edit files on directly on the server. Click on the file and open it in TextMate. When you save it, the file on the server is changed. As our team has grown in numbers as well as in the level of collaboration that we achieve, editing files live on the server has become less practical, and safe. The IM messages, “yo, are you editing profile.php? I need to update it,” used to be oh so common. They’re now a thing of the past.

Currently, we use TextMate and edit local copies of the website. We each have our own development server (aka sandbox), and when we’ve got some code that’s ready, we’ll check it in to our Subversion repository. Subversion is a magical creature that will solve all your software development version control woes. Even if you work alone, it’s worthwhile. I’ve written about subversion before, so I’ll leave it at that. Anyway, with some TextMate macros that run subversion and rsync, we rarely have to leave TextMate to check out code, edit, save, push up to the development server, and check in code.

Back to Coda. They released version 1.0 many months ago and there were some things that just didn’t allow it to fit into the workflow, such as lack of scripting and subversion support. They’ve surely heard this from many, many developers as they’ve added many features, including Subversion support. Sweet.

So Why Can’t I Use Coda?

I downloaded the trial, set it up for one of our websites and headed directly to the Subversion tools. Bang. brick wall.

Now I know that “stdin: is not a tty” warning message all too well. I see it every time I do a subversion update in TextMate

or of course on the command line

But it is just a warning and doesn’t break the subversion operation.

It does seem to stop Coda in its tracks. Boooo.

My understanding is that this is caused by a script running in a shell resource file somewhere that is expecting interactive mode and complains when it’s run from subversion. Word on the street is that it’s specifically caused by the mesg unix command. For the life of me, I cannot find anything like that in any of my resource files, mine or system defaults.

Anyone Listening?

I’d love to get this working. Anyone have any suggestions on what’s causing this error? Or otherwise, what can I do to get Coda to not choke on it?

The Coda guys must have seen this before. Help!