ericnakagawa's dashboard

Neil Haranhalli started following the idea "Date Ranges for Basecamp!" in 37signals.

Scott Fleckenstein replied on November 12, 2008 08:40 to the idea "You should allow us to import our bundles from TextMate" in Panic:

Hot Damn!

/me runs to go try out new software

Steven Frank replied on November 12, 2008 06:18 to the idea "You should allow us to import our bundles from TextMate" in Panic:

Coda 1.6 now features a plug-in interface with a high-level of compatibility with TextMate bundle commands. We think this will help you do the sorts of things you used to do with TextMate bundles. Let us know if we missed something.

Steven Frank replied on November 12, 2008 06:15 to the idea "Coda + SVN = Booya" in Panic:

SVN support was added in 1.5! Thanks, all.

ee replied on September 25, 2008 14:21 to the idea "Coda + SVN = Booya" in Panic:

Versions (beta 5) included a Subversion library that is not compatible with the default svn command line tool installed on Leopard. If you checked out a working copy with Versions b5, the default svn command line tool (and Coda) will not recognize that working copy.

Panic said to fix this problem you can trash the working copy you checked out with Versions b5 and re-checkout a working copy with Coda or the default 'svn' command line tool. Although probably goes without say, but, MAKE SURE TO CHECK-IN ANY UNCOMMITTED CHANGES BEFORE TRASHING YOUR LOCAL COPY.

KarlRoos replied on September 25, 2008 12:18 to the idea "Coda + SVN = Booya" in Panic:

It doesn't work really good for me with my Google Code SVN repository.
Maybe I'm just a noob with SVN but it does work for me in Versions...

Kody Riker started following the question "STOP Annoying Weekly Billing Emails" in DreamHost.

Louis St-Amour replied on August 28, 2008 16:08 to the idea "Coda + SVN = Booya" in Panic:

Yay. Just saw the email. I knew there was a reason I bought Coda.

BolochDE replied on August 27, 2008 11:31 to the idea "Coda + SVN = Booya" in Panic:

svn in coda sucks atm, doesnt work in my project folders, still using versions...

Eric Case replied on August 27, 2008 06:45 to the idea "Coda + SVN = Booya" in Panic:

w00t!

eh replied on August 27, 2008 05:52 to the idea "Coda + SVN = Booya" in Panic:

SVN is in Coda 1.5!

http://www.panic.com/coda/

ericnakagawa replied on August 25, 2008 11:55 to the problem "Our @Lulzftw account no longer allows us to post tweets." in Twitter:

3 days in. Any news?

A comment on the problem "Our @Lulzftw account no longer allows us to post tweets." in Twitter:

While I do appreciate the information about Twitter hiring additional help to handle the Trouble Tickets... Sadly, I'm not seeing how it's relevant to the problem at hand or the solution to our problem. – ericnakagawa, on August 22, 2008 20:07

minjungkim replied on August 22, 2008 11:28 to the problem "Our @Lulzftw account no longer allows us to post tweets." in Twitter:

FWIW: I've been hand managing adding and msging folks from the @lulzftw site. Adding folks who follow or twitter about icanhascheezburger.com and lolcats as it's related content to what folks may be interested in for the book. I don't consider that spamming. Especially when you consider the ratio of following to followers at a manageable 3:1/ 4:1 ratio.

A comment on the problem "Our @Lulzftw account no longer allows us to post tweets." in Twitter:

Unfortunately, I'm not aware of an "expedited" list, though I'm sure a lot of people wish there was such a list! haha! It's my understanding that they deal with the tickets sequentially in the order they come in. – mdy, on August 22, 2008 09:25

A comment on the problem "Our @Lulzftw account no longer allows us to post tweets." in Twitter:

mdy... What do we need to do to get on the "expedited" list? Do I need to ask @ev directly? – ericnakagawa, on August 22, 2008 09:16

A comment on the problem "Our @Lulzftw account no longer allows us to post tweets." in Twitter:

Yes, unfortunately.... Twitter support has been swamped lately because of all the spam that's been hitting them. I *did* see earlier today on the Twitter blog that they're hiring two more people to help out and that one of them is starting next week. So I'm hopeful that the turn-around on support requests will improve after that. Anyway, I hope your issue gets fixed soon. – mdy, on August 22, 2008 09:10

A comment on the problem "Our @Lulzftw account no longer allows us to post tweets." in Twitter:

Yes Mdy. That's exactly what I mean. Still waiting. 3-5 days? Wow. Really? Wow. – minjungkim, on August 22, 2008 08:53

A comment on the problem "Our @Lulzftw account no longer allows us to post tweets." in Twitter:

Hello. Just double checking -- when you say you've "written a comment back," did you mean you logged a support ticket, received a confirmation email with a ticket number, and you've posted an update to the support ticket? If yes, then it should just be a matter of time before you get a reply. There's usually a backlog of 3 to 5 working days, depending on how swamped the support guys are. – mdy, on August 22, 2008 08:42

minjungkim replied on August 22, 2008 06:27 to the problem "Our @Lulzftw account no longer allows us to post tweets." in Twitter:

And by the way, the fact that it's been busted for about 3-4 days and only got "flagged as suspended" today *after* the get satisfaction msg is more than just a little stupid.

Like "Oh... we don't have a reason for why it's broke, why don't we call it out as suspended *now* that they've noticed and started making a request for support"