Emacs and Leopard problems continue

[Rob MacLeod]

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 at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo/macports-users
>