Apple

On Nov 19, 2013, at 8:37 PM, Jeff Kelley <email@hidden> wrote:

I have seen similar behavior with Xcode 4.6.3 under Mavericks and code folding. In that case, you’re able to fix the problem by selecting Editor -> Code Folding -> Unfold All.

Jeff Kelley

email@hidden | @SlaunchaMan | jeffkelley.org

On Tue, Nov 19, 2013 at 2:01 PM, Owen Hartnett <email@hidden> wrote:
Here's some behavior that it took me a couple of days to track down:

XCode 4.6.3 running under Mavericks

Made some code changes in a file and the Xcode editor started hallucinating:

1) would display the file correctly at first
2) after a seeming random amount of time it would pervert where all the line breaks were, instead of seeing:

int i = someFunction(x);

it would look more like:

int i =
s
omeFunct
ion(x
);

In addition, the file would not be editable, and the line numbers which I had displayed on the left now disappeared, except the very first line in the file had a line number like 1624.

3) clicking another file in the list to edit in the window showed a good file, and after clicking a few more files in the list, you could open the original file again, and it would either still be perverted, but perhaps starting at a different (sometimes lower in the file) place, or it would be fine for a while, then spazz out again.

4) Didn't happen with Xcode 5.

5) Even though the code looked hosed, looking at it in BBEdit showed it was still in the original state on disk, even though I had run it and Xcode displayed corruption.

The problem and solution: I had typed in the beginning of an api call which I planned to use after I had debugged some other existing code. Autofill had added the whole call, and used the funny balloon things as a placeholder for arguments. I didn't replace the balloon, but I immediately commented out the code with a //. The line was:

//[self checkAndRemoveDeletedItems:items AtCurrentNode: (MobileItemNode *) :items];

(with the text (MobileItemNode *) in an Xcode provided balloon.)

Yes, the balloon was giving the IDE all kinds of fits. Removing the commented out line restored Xcode to sanity. I never was able to debug the original code because of the distraction and so the offending balloons stayed there while I tried replacing the file from source control, reinstalling Xcode 4, Looking through the pbxproj file for weird things and generally wondered how the impossible was possible.

So, I thought I'd pass this as a warning to my fellow travelers, many of you like me, still using Xcode 4.6.3.

-Owen
_______________________________________________
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

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

References:

>Xcode 4.6.3+Mavericks+commented balloons induce hallucinations (From: Owen Hartnett <email@hidden>)

>Re: Xcode 4.6.3+Mavericks+commented balloons induce hallucinations (From: Jeff Kelley <email@hidden>)

Prev by Date: git-modified status flickers between M and blank in 5.0.2

Next by Date: Instruments and dtrace

Previous by thread: Re: Xcode 4.6.3+Mavericks+commented balloons induce hallucinations

Next by thread: Re: Any easy way to see the whole error?

Index(es):

Date

Thread