Re: Can't launch carbon XEmacs
Re: Can't launch carbon XEmacs
- Subject: Re: Can't launch carbon XEmacs
- From: Kurt Bigler <email@hidden>
- Date: Mon, 14 Mar 2005 16:38:44 -0800
on 3/13/05 10:25 AM, Skip Montanaro <email@hidden> wrote:
> Thanks for the responses regarding my Carbon XEmacs launch problems.
> Stephen Turnbull, one of the main XEmacs maintainers, put up his XEmacs.app
> directory on a website where I could snatch it. I downloaded and untarred
> it. It launched just fine. A recursive diff showed no differences other
> than obvious things like the XEmacs executable itself. In particular, the
> Info.plist and PkgInfo files were identical and the overall structure of
> XEmacs.app was the same.
>
> I then tried this with my *non-functioning* XEmacs.app:
>
> % tar cf - XEmacs.app | (cd ~/tmp ; tar xvf -)
>
> then launched ~/tmp/XEmacs.app. It launched just fine. Does this sort of
> behavior ring a bell with anyone?
>
> The XEmacs folks also created a CVS branch for Andrew Choi's code. I
> checked that out and built it. It also launches properly.
>
> I'm perplexed, but somehow seem to have stumbled past whatever was blocking
> my path. This morning I went back to the XEmacs 21.5.18 distribution,
> applied Andrew's patch and built. The result also launches more-or-less
> properly
[snip]
> Unfortunately, now that I have deleted, rebuilt, tarred/untarred to my
> heart's content, I no longer have a failing XEmacs.app. Go figure...
I have had app bundles go between doing nothing on a double-click (with no
error message) and triggering the damaged bundle error you were seeing. I
have also had app bundles go from not working to working and back. Both
types of changes were for no apparent reason. Messing with something in the
bundle, changing it, changing it back, for example might trigger a change in
behavior. Often behavior would then revert spontaneously back to a previous
behavior.
This was with a hand-contrusted bundle. Possibly XCode does something to
notify the Finder of changes to an app bundle, which you can't do when
constructing one by hand. I suspect there is some cached state involved,
perhaps in the Finder, perhaps in launch services.
All this makes diagnosing problems very difficult.
-Kurt
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden