emacs-app: update to 23.1

[css@…]

Now that emacs 23.1 has been released, update the emacs-app port to use the official emacs version. Or should this port be removed and turned into an emacs port variant? Since the build configuration is quite different, it might be best to keep emacs-app as a separate port.

[bob.spamnot@…]

I agree that the cocoa version should be in a separate port (emacs-app) and the plain emacs port should be the X11 variants (X11 and gtk, especially). The carbon variant needs to be removed.

[dports@…]

I was just playing around with emacs 23.1 myself -- I've attached the portfile I used. Seems to work so far, although I haven't done much with it yet. FWIW, I've also been using a recent cvs build of emacs (ala emacs-app-devel but with a more recent cvs snapshot) for a couple weeks with no problems.

[dports@…]

Cc Me!

[css@…]

I'm out of town this week (sans Mac!), but I'll give the release version a whirl this weekend.

[dports@…]

Someday, it would also be nice to have the port build a couple wrappers for the new daemon mode that we could put in /Applications, one that launches emacs --daemon and could be added as a LoginItem, and one that runs emacsclient. I'd look into putting them together now, but the point is moot at the moment -- currently, daemon mode doesn't seem to work with the Aqua interface. I filed a bug against emacs upstream about this (#4070).

[jeff@…]

An initial Portfile for 23.1 is available  on github.

[css@…]

Replying to jeff@…:

An initial Portfile for 23.1 is available  on github.

This seems like it works well ... was there a particular reason you removed the custom site-start.el? This file made Emacs.app load lisp files installed by other ports into ${prefix}/share/emacs.

[css@…]

updated Portfile to include loading from prefix

[dports@…]

Replying to css@…:

This seems like it works well ... was there a particular reason you removed the custom site-start.el? This file made Emacs.app load lisp files installed by other ports into ${prefix}/share/emacs.

I left it out in the first portfile I updated too -- in my case, at least, it was purely an oversight. I forgot to attach the updated portfile (which I've been using for a few days). I was going to attach it now, but yours looks identical, so... :-)

[css@…]

Committed to r55596!