On Sep 15, 2011, at 2:34 PM, Jerry Krinock wrote: > Bang. Just do a ⇧⌘F, copy that 13476 to the search field, and in seconds the > problem is staring me in the face. > > __FILE__ would be useful if it didn't print out the whole damned full path.
Interesting, never thought of that. I prefer the file path & function name myself, but that's just me. > Unfortunately, I remember learning once that Xcode's regex does not parse > newlines, and just confirmed that still seems to be the case. So the \n on > the end breaks it, and without it, I'm left with a blank line. Some regex syntaxes won't parse past a line end unless you use a special flag or modifier. I really don't use Xcode regex, so I can't say more, except perhaps for this you could just do it outside Xcode. -- Scott Ribe scott_r...@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
