Comments on: Restart Xcode

By: Henrik N

Henrik N — Fri, 19 Jan 2007 08:14:26 +0000

I use Quicksilver to relaunch projects - I set MyProject.xcodeproj as the default for “MyProject” (⌃+click a result, “Set as Default for …”), so I can just trigger QS, type the name of my project and launch it in Xcode.

My Xcode restarts have decreased dramatically, though, since I realized the reason I sometimes got un-closeable (until Xcode reboot) instances of my built-and-gone app, was that a debugger window had opened and needed me to “Terminate”.

By: Richy

Richy — Thu, 18 Jan 2007 16:42:50 +0000

I’m constantly amazed by how useful AppleScript is, part of the reason I regularly read this blog.. :)

Oh and thanks for the Relaunch plug dgohara :) I was going to mention that it does, indeed, support XCode.

By: Mark Dalrymple

Mark Dalrymple — Wed, 17 Jan 2007 23:25:14 +0000

People may deride emacs for whatever reason, but I frequently enjoy 30+ day uptimes of a single session. Even with a couple hundred files open and several 30+ day shell sessions, it’s still a smaller (real and virtual) process than things like GrowlHelper, translate, coreservicesd, mds, and every graphical app.

By: dgohara

dgohara — Wed, 17 Jan 2007 21:04:54 +0000

I just did a quick application note on a program called Relaunch. It’s very good and works with a lot of applications, including Xcode. See my note about orphaned windows though.

http://www.macresearch.org/application_relaunch

By: Jens Ayton

Jens Ayton — Wed, 17 Jan 2007 19:43:23 +0000

While I’m not prepared to select one very-worst Xcode bug – there are so many to choose from – the one Joachim mentions is indeed a serious candidate.

By: Petteri Kamppuri

Petteri Kamppuri — Wed, 17 Jan 2007 19:19:54 +0000

Thanks! This script will save me a lot of time. What I did was I saved it as an application and put it to a location where Quicksilver can find it. Oh the joy!

I think I’ve run into the the save-quick-build bug a few times. I just didn’t realize it could be that. But a few times I haven’t seen any of the new behaviour I’ve just coded until I build and run again. Thanks to Joachim for pointing this bug out, now I’m more aware of it.

By: Daniel Jalkut

Daniel Jalkut — Wed, 17 Jan 2007 17:57:33 +0000

Joachim: sure, the recent items work. But that’s just more brain cells I have to waste on filtering through noise. You also typically have to wait while Xcode slogs through opening one, before you can get it responsive enough to open another. Scripts are ideal for these types of repetitive nuisances.

I haven’t seen the save-quick-build bug you’re describing. Thankfully!

By: Joachim Bengtsson

Joachim Bengtsson — Wed, 17 Jan 2007 17:53:57 +0000

File > Recent Projects doesn’t work…?

Oh, and the MOST annoying bug of all time must be the one where, when you save and then build semi-quickly thereafter, the build uses an OLD version of the file! So you get bugs because you probably saved before it was done… This is most annoying when you don’t get a compilation error, all that happens is that you get an old version, and you get frustrated because *nothing that you coded works or even shows up*! Until you build again. I haven’t found a 100% way to reproduce it, though…