Re: Emacs and Leopard problems continue

Eric> ... I search Google for "emacs site:apple.com". A quick scan Eric> later, and I get back to: Eric>

Re: Emacs and Leopard problems continue

On Feb 5, 2008, at 10:53 AM, [EMAIL PROTECTED] wrote: "Jordan" == Jordan K Hubbard <[EMAIL PROTECTED]> 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

Re: Emacs and Leopard problems continue

> "Jordan" == Jordan K Hubbard <[EMAIL PROTECTED]> 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> wou

Re: Emacs and Leopard problems continue

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 A

Re: Emacs and Leopard problems continue

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

Re: Emacs and Leopard problems continue

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 sta

Re: Emacs and Leopard problems continue

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:1

Re: Emacs and Leopard problems continue

On 05.02.2008, at 01:30, Rob MacLeod wrote: With the Carbon and Aqua emacs, I also have a hard time finding where to place additional LISP code for tools that I find or write to extend emacs. It is all very simple and stable in the X11 versions. Just put them into ~/.emacs ... I am even

Re: Emacs and Leopard problems continue

On 5 Feb 2008, at 00:30, Rob MacLeod wrote: Hi, Hi How do you select fonts for Carbon and Aqua emacs ? I find that X has nicer fixed pitch fonts than the native windows. On Aquamacs, hit Command-T With the Carbon and Aqua emacs, I also have a hard time finding where to place addi

Re: Emacs and Leopard problems continue

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 list

Re: Emacs and Leopard problems continue

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

Re: Emacs and Leopard problems continue

Hi, How do you select fonts for Carbon and Aqua emacs ? I find that X has nicer fixed pitch fonts than the native windows. With the Carbon and Aqua emacs, I also have a hard time finding where to place additional LISP code for tools that I find or write to extend emacs. It is all very s

Re: Emacs and Leopard problems continue

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

Re: Emacs and Leopard problems continue

On 4 Feb 2008, at 15:17, Rob MacLeod wrote: I totally agree about the desirability of an X11 port for its look and feel. I have tried all the Carbon and Aqua ports I have come across and none of them are superior (and most inferior) to the tried and true. I find it hard to understand h

Re: Emacs and Leopard problems continue

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 lin

Re: Emacs and Leopard problems continue

Mark, I totally agree about the desirability of an X11 port for its look and feel. I have tried all the Carbon and Aqua ports I have come across and none of them are superior (and most inferior) to the tried and true. Thanks for the patch. I will try it out and report any problems. As

Re: Emacs and Leopard problems continue

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 w

Re: Emacs and Leopard problems continue

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

Re: Emacs and Leopard problems continue

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

Re: Emacs and Leopard problems continue

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

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, neit