Re: Beating XCode's key buffer
Re: Beating XCode's key buffer
- Subject: Re: Beating XCode's key buffer
- From: Steve Mills <email@hidden>
- Date: Thu, 16 Feb 2006 08:03:52 -0600
On Feb 16, 2006, at 00:53, Justin Drury <email@hidden>
wrote:
Working on a fairly large implementation file, hit command S, command
R, occasionally not all the changes to that file are committed before
the build begins. Quite often I get build errors(missing ; for
example, even though I typed it just before I saved!) leaving me
scratching my head. I've just gotten in the habit of on error's
trying a build again, usually it works just fine!
Yes, I've seen similar results - debugging code that really didn't
get compiled in the most recent build. Another one that really bugs
me is when I'm searching for something in a file and I quickly hit
these 3 key equivs; command-e (Use Selection for Find), command-up-
arrow, command-g (Find Next). The Find Next just beeps. If I give
Xcode a split second to catch up with a slow, puny, inferior human,
then command-g works.
I really miss the days (like just a few months ago) when my dev
environment could keep up with me and didn't make me waste 5 minutes
(n times every day) waiting for the app to be debugged after making 1
tiny change. Or waiting a few minutes for the SPOD to stop spinning
after I add a file to the project or move it within the target.
Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.com/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden