Emacs and Leopard problems continue

[Jordan K. Hubbard]

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 at gmx.at>
>>>>
>>>> "[T]his is not a disentanglement from, but a progressive knotting  
>>>> into."
>>>>
>>>
>>
>