Emacs and Leopard problems continue
Hi folks, I am still struggling with Leopard woes with emacs. I was able to get emacs, emacs-devel, and emacs-app all made by manually applying the patch provided in ticket #13294. emacs made in the wrong directory while emacs-devel did better and ended up properly placed. However, neither emacs nor emacs-devel launch a new X window when I start them. I vaguely recall that this was a problem in the past but I was able with Tiger to get at least one of them (no longer sure which) to work in the proper X window mode. Does anyone know if there are some other settings I need to get a full functioning X11 based emacs to work? In the meantime, I will experiment with emacs-app to see if I can get it to work the way I am used to... Good thing this is the break and I have time to deal with all the frustrations of Leopard.... Happy New Year, Rob
OK, I'll bite. What specifically is wrong with the system emacs that requires folks to struggle so hard to build another copy? It even supports carbon if you add an app wrapper (like the one I just attached - a mere 55k, and most of that is the icon), so I'm not sure what would lead one to struggle so hard to build emacs again. Yes, the macports version should certainly work just on general principle, but that's not the question I'm asking. - Jordan p On Dec 31, 2007, at 2:58 PM, Rob MacLeod wrote:
Hi folks,
I am still struggling with Leopard woes with emacs.
I was able to get emacs, emacs-devel, and emacs-app all made by manually applying the patch provided in ticket #13294. emacs made in the wrong directory while emacs-devel did better and ended up properly placed.
However, neither emacs nor emacs-devel launch a new X window when I start them. I vaguely recall that this was a problem in the past but I was able with Tiger to get at least one of them (no longer sure which) to work in the proper X window mode.
Does anyone know if there are some other settings I need to get a full functioning X11 based emacs to work?
In the meantime, I will experiment with emacs-app to see if I can get it to work the way I am used to...
Good thing this is the break and I have time to deal with all the frustrations of Leopard....
Happy New Year,
Rob
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Hi, This is pretty easy--I want emacs to work in X11. Cheers, Rob On Jan 1, 2008, at 1:16 PM, Jordan K. Hubbard wrote:
OK, I'll bite. What specifically is wrong with the system emacs that requires folks to struggle so hard to build another copy? It even supports carbon if you add an app wrapper (like the one I just attached - a mere 55k, and most of that is the icon), so I'm not sure what would lead one to struggle so hard to build emacs again. Yes, the macports version should certainly work just on general principle, but that's not the question I'm asking.
- Jordan
<Emacs.app>
p On Dec 31, 2007, at 2:58 PM, Rob MacLeod wrote:
Hi folks,
I am still struggling with Leopard woes with emacs.
I was able to get emacs, emacs-devel, and emacs-app all made by manually applying the patch provided in ticket #13294. emacs made in the wrong directory while emacs-devel did better and ended up properly placed.
However, neither emacs nor emacs-devel launch a new X window when I start them. I vaguely recall that this was a problem in the past but I was able with Tiger to get at least one of them (no longer sure which) to work in the proper X window mode.
Does anyone know if there are some other settings I need to get a full functioning X11 based emacs to work?
In the meantime, I will experiment with emacs-app to see if I can get it to work the way I am used to...
Good thing this is the break and I have time to deal with all the frustrations of Leopard....
Happy New Year,
Rob
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Jordan K. Hubbard wrote:
OK, I'll bite. What specifically is wrong with the system emacs that requires folks to struggle so hard to build another copy? It even supports carbon if you add an app wrapper (like the one I just attached - a mere 55k, and most of that is the icon), so I'm not sure what would lead one to struggle so hard to build emacs again. Yes, the macports version should certainly work just on general principle, but that's not the question I'm asking.
I was going to reply that /usr/bin/emacs is only emacs-21, but then I just noticed that Mac OS X 10.5 Leopard apparently ships with emacs-22. Still, having the latest stable Emacs is a plausible desire for users still with Mac OS X 10.4 Tiger. A second plausible use case might be to use MacPorts for the packaging of various Emacs-modes (SLIME, nxml-mode, haskell-mode, etc.), offering an infrastructure for their timely updating. -- <Mark.Evenson@gmx.at> "[T]his is not a disentanglement from, but a progressive knotting into."
I was not able to get the Leopard shipped version of emacs to fire up an X window. All it would do was drive the terminal window (or X11 xterm) from which I launched it. This is not acceptable, of course. I was able to download the generic emacs from the gnu site, apply the patch that I got from the Macports edition of emacs, and then get it to both build and work. So why is the version on MacPorts still so lame? Is there someone maintaining this package? Cheers, Rob On Feb 4, 2008, at 6:19 AM, Mark Evenson wrote:
Jordan K. Hubbard wrote:
OK, I'll bite. What specifically is wrong with the system emacs that requires folks to struggle so hard to build another copy? It even supports carbon if you add an app wrapper (like the one I just attached - a mere 55k, and most of that is the icon), so I'm not sure what would lead one to struggle so hard to build emacs again. Yes, the macports version should certainly work just on general principle, but that's not the question I'm asking.
I was going to reply that /usr/bin/emacs is only emacs-21, but then I just noticed that Mac OS X 10.5 Leopard apparently ships with emacs-22. Still, having the latest stable Emacs is a plausible desire for users still with Mac OS X 10.4 Tiger.
A second plausible use case might be to use MacPorts for the packaging of various Emacs-modes (SLIME, nxml-mode, haskell-mode, etc.), offering an infrastructure for their timely updating.
-- <Mark.Evenson@gmx.at>
"[T]his is not a disentanglement from, but a progressive knotting into."
Rob MacLeod wrote:
I was not able to get the Leopard shipped version of emacs to fire up an X window. All it would do was drive the terminal window (or X11 xterm) from which I launched it. This is not acceptable, of course.
Mac OS X 10.5 Leopard's /usr/bin/emacs is not linked to X11: it will only work within a Terminal.app, an xterm, or anything that supports a termcap entry (you can verify this via "otool -L /usr/bin/emacs" which shows that it is not linked against X11 libaries). Personally, I like using the X11 version under OS X to give consistency to my emacs experience across UNIX/Max OS X development. And I never really totally understand the need to "Carbonize" or "Aquaify" the port, although Cut and Paste with the Mac OS X clipboard sometimes acts a little wonky (tip: use the Emacs menu item for Paste when CMD-v fails to insert properly). But maybe the cute Emacs icon has something to do with it, like being able to switch via the OS X switcher (and the 'emacs-app' port icon is even better!)
I was able to download the generic emacs from the gnu site, apply the patch that I got from the Macports edition of emacs, and then get it to both build and work. So why is the version on MacPorts still so lame? Is there someone maintaining this package?
I have submitted a patch [1] to the current ticket within MacPorts Trac, and am trying to get it promoted through to commit to the tree (I am a maintainer for some MacPorts, although not editors/emacs, but do not have commit rights.) I agree that the response time on fixing this has been "lame", but calling the port "lame" is a trifle over the top, don't you think? Not a great way to win friends and influence people. . . [1]: http://trac.macports.org/projects/macports/ticket/13942 Some instructions for using my patch for those who are following from the sidelines: 1. Pick a spot to build the port, like osx$ mkdir ~/ports 2. Copy the existing emacs build infrastructure over: osx$ cp -pr `port dir emacs` ~/ports 3. Replace the existing 'Portfile' with my [trivially patch][2]: [2]: http://trac.macports.org/projects/macports/attachment/ticket/13942/emacs-Por... osx$ cd ~/ports/emacs osx$ wget http://trac.macports.org/projects/macports/attachment/ticket/13942/emacs-Por... osx$ patch -p0 < emacs-Portfile.diff 4. Add the [upstream emacs patch to the files directory][3] [3]: http://trac.macports.org/projects/macports/attachment/ticket/13942/patch-src... osx$ cd ~/ports/emacs/files osx$ wget http://trac.macports.org/projects/macports/attachment/ticket/13942/patch-src... 5. Build and install: osx$ cd ~/ports/emacs osx$ sudo port -D . install When the official Portfile gets updated, this change will be automatically overridden by a normal 'port upgrade outdated' procedure. -- <Mark.Evenson@gmx.at> "[T]his is not a disentanglement from, but a progressive knotting into."
On Feb 4, 2008, at 6:19 AM, Mark Evenson wrote:
Jordan K. Hubbard wrote:
OK, I'll bite. What specifically is wrong with the system emacs that requires folks to struggle so hard to build another copy? It even supports carbon if you add an app wrapper (like the one I just attached - a mere 55k, and most of that is the icon), so I'm not sure what would lead one to struggle so hard to build emacs again. Yes, the macports version should certainly work just on general principle, but that's not the question I'm asking.
I was going to reply that /usr/bin/emacs is only emacs-21, but then I just noticed that Mac OS X 10.5 Leopard apparently ships with emacs-22. Still, having the latest stable Emacs is a plausible desire for users still with Mac OS X 10.4 Tiger.
A second plausible use case might be to use MacPorts for the packaging of various Emacs-modes (SLIME, nxml-mode, haskell-mode, etc.), offering an infrastructure for their timely updating.
-- <Mark.Evenson@gmx.at>
"[T]his is not a disentanglement from, but a progressive knotting into."
-- <Mark.Evenson@gmx.at> "[T]his is not a disentanglement from, but a progressive knotting into."
On Feb 4, 2008, at 5:46 AM, Rob MacLeod wrote:
I was not able to get the Leopard shipped version of emacs to fire up an X window. All it would do was drive the terminal window (or X11 xterm) from which I launched it. This is not acceptable, of course.
The leopard shipped emacs is linked with Carbon. You don't NEED X for that version if you use the app wrapper I sent out - it supports the NATIVE window system. And if you prefer X11 to the native window system, well, it's just possible that you might be happier installing Linux or *BSD on your machine. - Jordan
I was able to download the generic emacs from the gnu site, apply the patch that I got from the Macports edition of emacs, and then get it to both build and work. So why is the version on MacPorts still so lame? Is there someone maintaining this package?
Cheers, Rob
On Feb 4, 2008, at 6:19 AM, Mark Evenson wrote:
Jordan K. Hubbard wrote:
OK, I'll bite. What specifically is wrong with the system emacs that requires folks to struggle so hard to build another copy? It even supports carbon if you add an app wrapper (like the one I just attached - a mere 55k, and most of that is the icon), so I'm not sure what would lead one to struggle so hard to build emacs again. Yes, the macports version should certainly work just on general principle, but that's not the question I'm asking.
I was going to reply that /usr/bin/emacs is only emacs-21, but then I just noticed that Mac OS X 10.5 Leopard apparently ships with emacs-22. Still, having the latest stable Emacs is a plausible desire for users still with Mac OS X 10.4 Tiger.
A second plausible use case might be to use MacPorts for the packaging of various Emacs-modes (SLIME, nxml-mode, haskell-mode, etc.), offering an infrastructure for their timely updating.
-- <Mark.Evenson@gmx.at>
"[T]his is not a disentanglement from, but a progressive knotting into."
Huh? Because I like X11 for certain apps, I am supposed to run Linux? Is this supposed to be a joke or a snide remark? On Feb 4, 2008, at 12:18 PM, Jordan K. Hubbard wrote:
On Feb 4, 2008, at 5:46 AM, Rob MacLeod wrote:
I was not able to get the Leopard shipped version of emacs to fire up an X window. All it would do was drive the terminal window (or X11 xterm) from which I launched it. This is not acceptable, of course.
The leopard shipped emacs is linked with Carbon. You don't NEED X for that version if you use the app wrapper I sent out - it supports the NATIVE window system.
And if you prefer X11 to the native window system, well, it's just possible that you might be happier installing Linux or *BSD on your machine.
- Jordan
I was able to download the generic emacs from the gnu site, apply the patch that I got from the Macports edition of emacs, and then get it to both build and work. So why is the version on MacPorts still so lame? Is there someone maintaining this package?
Cheers, Rob
On Feb 4, 2008, at 6:19 AM, Mark Evenson wrote:
Jordan K. Hubbard wrote:
OK, I'll bite. What specifically is wrong with the system emacs that requires folks to struggle so hard to build another copy? It even supports carbon if you add an app wrapper (like the one I just attached - a mere 55k, and most of that is the icon), so I'm not sure what would lead one to struggle so hard to build emacs again. Yes, the macports version should certainly work just on general principle, but that's not the question I'm asking.
I was going to reply that /usr/bin/emacs is only emacs-21, but then I just noticed that Mac OS X 10.5 Leopard apparently ships with emacs-22. Still, having the latest stable Emacs is a plausible desire for users still with Mac OS X 10.4 Tiger.
A second plausible use case might be to use MacPorts for the packaging of various Emacs-modes (SLIME, nxml-mode, haskell-mode, etc.), offering an infrastructure for their timely updating.
-- <Mark.Evenson@gmx.at>
"[T]his is not a disentanglement from, but a progressive knotting into."
Rob MacLeod wrote:
Hi folks,
I am still struggling with Leopard woes with emacs.
I was able to get emacs, emacs-devel, and emacs-app all made by manually applying the patch provided in ticket #13294. emacs made in the wrong directory while emacs-devel did better and ended up properly placed. I only tried the GTK version, which worked for me after patching it. If that is acceptable you could try installing emacs +gtk.
Kendall
A little bit of both. You didn't say you "liked X11 for certain apps", you stated that it was "not acceptable" for the shipping Leopard version of emacs to support the native window system in lieu of your favorite one. If I were a Linux user and I came barging into the Redhat mailing lists saying that it was not acceptable for the shipping RedHat version of emacs to only support X11 since Sun's NeWS was my favorite window system, I'd be laughed (or worse) right out of the mailing list in question. You're free to compile your own version of emacs. You're also more than free to do it strictly on your own since tossing around language like "unacceptable" or "lame" will not win you much support on these mailing lists, the MacPorts folks certainly not being paid to support emacs for you (nor am I being paid to support anything but the most MacOSX-centric configuration, which does not mean emacs/x11). - Jordan On Feb 4, 2008, at 4:23 PM, Rob MacLeod wrote:
Huh? Because I like X11 for certain apps, I am supposed to run Linux? Is this supposed to be a joke or a snide remark?
On Feb 4, 2008, at 12:18 PM, Jordan K. Hubbard wrote:
On Feb 4, 2008, at 5:46 AM, Rob MacLeod wrote:
I was not able to get the Leopard shipped version of emacs to fire up an X window. All it would do was drive the terminal window (or X11 xterm) from which I launched it. This is not acceptable, of course.
The leopard shipped emacs is linked with Carbon. You don't NEED X for that version if you use the app wrapper I sent out - it supports the NATIVE window system.
And if you prefer X11 to the native window system, well, it's just possible that you might be happier installing Linux or *BSD on your machine.
- Jordan
I was able to download the generic emacs from the gnu site, apply the patch that I got from the Macports edition of emacs, and then get it to both build and work. So why is the version on MacPorts still so lame? Is there someone maintaining this package?
Cheers, Rob
On Feb 4, 2008, at 6:19 AM, Mark Evenson wrote:
Jordan K. Hubbard wrote:
OK, I'll bite. What specifically is wrong with the system emacs that requires folks to struggle so hard to build another copy? It even supports carbon if you add an app wrapper (like the one I just attached - a mere 55k, and most of that is the icon), so I'm not sure what would lead one to struggle so hard to build emacs again. Yes, the macports version should certainly work just on general principle, but that's not the question I'm asking.
I was going to reply that /usr/bin/emacs is only emacs-21, but then I just noticed that Mac OS X 10.5 Leopard apparently ships with emacs-22. Still, having the latest stable Emacs is a plausible desire for users still with Mac OS X 10.4 Tiger.
A second plausible use case might be to use MacPorts for the packaging of various Emacs-modes (SLIME, nxml-mode, haskell-mode, etc.), offering an infrastructure for their timely updating.
-- <Mark.Evenson@gmx.at>
"[T]his is not a disentanglement from, but a progressive knotting into."
Disclaimer: I am happy with my configured Aquamacs on Mac OS X, but essentially I have configured it to work like a plain GNU Emacs: no toolbar, only a single window, and most other "fancy Mac specials" it provides I'd probably also switch off). It's great that way;-) On 04.02.2008, at 20:18, Jordan K. Hubbard wrote:
The leopard shipped emacs is linked with Carbon. You don't NEED X for that version if you use the app wrapper I sent out - it supports the NATIVE window system.
How is one supposed to find that out?
otool -L /usr/bin/emacs /usr/bin/emacs: /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.0.0)
Why is Emacs.app not part of Mac OS X? When / how long will this Carbon Emacs be supported? Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll
On Feb 5, 2008, at 12:32 AM, Jochen Küpper wrote:
The leopard shipped emacs is linked with Carbon. You don't NEED X for that version if you use the app wrapper I sent out - it supports the NATIVE window system.
How is one supposed to find that out?
Run emacs. :-) If you look at the startup screen text, you'll see: GNU Emacs 22.1.1 (mac-apple-darwin, Carbon Version 1.6.0) of 2008-01-30 on localhost
Why is Emacs.app not part of Mac OS X?
Some of us tried mightily to ship the app wrapper, but the look-and- feel just isn't up to snuff yet. I have to agree that it's pretty ugly, though I still think it would have been better to have it than not. Oh well. Perhaps we can work on improving the Carbon port in the interim.
When / how long will this Carbon Emacs be supported?
There are no plans to stop shipping it this way. - Jordan
>> How is one supposed to find that out? Jordan> Run emacs. :-) Jordan> If you look at the startup screen text, you'll see: GNU Emacs Jordan> 22.1.1 (mac-apple-darwin, Carbon Version 1.6.0) of 2008-01-30 on Jordan> localhost On my laptop /Applications/Emacs.app is dated Dec 3 2003. When I try to start it I get a crash dialog: The application Emacs quit unexpectedly. Mac OS X and other applications are not affected. ... [Ignore] [Report] [Relaunch] I imagine that got copied from my G4 laptop via SetupAssistant given what I found in the crash log: Process: Emacs [48538] Path: /Applications/Emacs.app/Contents/MacOS/Emacs Identifier: com.gnu.Emacs Version: ??? (???) Code Type: PPC (Translated) Parent Process: launchd [189] Should I have expected it to work? There's also something called EmacsStep.app in /Applications. That starts and runs, giving this summary of who he is: This is GNU Emacs 23.0.60.1 (i386-apple-darwin8.10.1, *Step 9.0rc3) of 2007-11-25 on hermes.mshome.net That app is dated Nov 25 2007. -- Skip Montanaro - skip@pobox.com - http://www.webfast.com/~skip/
I don't know where your /Applications/Emacs.app came from, but it wasn't Apple. You must have installed it at some point in the past and then nuked its support files or something. I would, in any case, delete it since you don't know how it got there. :) - Jordan On Feb 5, 2008, at 9:46 AM, skip@pobox.com wrote:
How is one supposed to find that out?
Jordan> Run emacs. :-)
Jordan> If you look at the startup screen text, you'll see: GNU Emacs Jordan> 22.1.1 (mac-apple-darwin, Carbon Version 1.6.0) of 2008-01-30 on Jordan> localhost
On my laptop /Applications/Emacs.app is dated Dec 3 2003. When I try to start it I get a crash dialog:
The application Emacs quit unexpectedly. Mac OS X and other applications are not affected. ... [Ignore] [Report] [Relaunch]
I imagine that got copied from my G4 laptop via SetupAssistant given what I found in the crash log:
Process: Emacs [48538] Path: /Applications/Emacs.app/Contents/MacOS/Emacs Identifier: com.gnu.Emacs Version: ??? (???) Code Type: PPC (Translated) Parent Process: launchd [189]
Should I have expected it to work?
There's also something called EmacsStep.app in /Applications. That starts and runs, giving this summary of who he is:
This is GNU Emacs 23.0.60.1 (i386-apple-darwin8.10.1, *Step 9.0rc3) of 2007-11-25 on hermes.mshome.net
That app is dated Nov 25 2007.
-- Skip Montanaro - skip@pobox.com - http://www.webfast.com/~skip/
"Jordan" == Jordan K Hubbard <jkh@apple.com> writes:
Jordan> I don't know where your /Applications/Emacs.app came from, but Jordan> it wasn't Apple. You must have installed it at some point in Jordan> the past and then nuked its support files or something. I Jordan> would, in any case, delete it since you don't know how it got Jordan> there. :) I know nothin' about support files. I went ahead and nuked it and will wait semi-patiently for a replacement. (Though I see there's a new version of Aquamacs.) Skip
On Feb 5, 2008, at 10:53 AM, skip@pobox.com wrote:
"Jordan" == Jordan K Hubbard <jkh@apple.com> writes:
Jordan> I don't know where your /Applications/Emacs.app came from, but Jordan> it wasn't Apple. You must have installed it at some point in Jordan> the past and then nuked its support files or something. I Jordan> would, in any case, delete it since you don't know how it got Jordan> there. :)
I know nothin' about support files. I went ahead and nuked it and will wait semi-patiently for a replacement. (Though I see there's a new version of Aquamacs.)
Whenever I find myself missing Emacs.app (or rather the packages that aren't available in the system version), I search Google for "emacs site:apple.com". A quick scan later, and I get back to: <http://www.apple.com/downloads/macosx/unix_open_source/carbonemacspackage.ht...
Not as satisfying as building your own, but life is sometimes too short. Eric
Eric> ... I search Google for "emacs site:apple.com". A quick scan Eric> later, and I get back to: Eric> <http://www.apple.com/downloads/macosx/unix_open_source/carbonemacspackage.ht... Excellent, thanks. Skip
participants (7)
-
Eric Gouriou
-
Jochen Küpper
-
Jordan K. Hubbard
-
Kendall Shaw
-
Mark Evenson
-
Rob MacLeod
-
skip＠pobox.com