Re: Emacs on OS X development

[Jan D.]

Leo skrev 2011-09-14 03:13:
> On 2011-09-14 02:43 +0800, John Wiegley wrote:
>> Thanks for the heads up.
>>
>> My biggest problem with the Emacs.app code -- and why I'm not using it 
>> anymore
>> -- is that subprocess communication is horribly laggy.  It makes several 
>> Emacs
>> services, such as flyspell, simply unusable.  "Mac port" Emacs doesn't have
>> this problem at all, such that flyspell works with the same speed it does on
>> Linux.
>>
>> People have commented about this flyspell issue many times, and from what 
>> I've
>> seen the blame keeps getting directed at aspell.  But actually, it's 
>> Emacs.app
>> that is the problem.  I've seen it with other things too, like Tramp and gdb,
>> though it's quite as pronounced there since users already expect to wait
>> longer.
> 
> I agree completely. People who have used macport would never want to go
> back to nsport. The difference is that noticeable. We have been hoping
> the nsport get better. It seems 3 years have passed.
> 

I tried it and went back.  That is because it is based on the Emacs 23 tree.

        Jan D.