[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: C-g crash in C-x C-f (OSX Lion)

From: YAMAMOTO Mitsuharu
Subject: Re: C-g crash in C-x C-f (OSX Lion)
Date: Fri, 23 Dec 2011 10:28:00 +0900
User-agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (Shijō) APEL/10.6 Emacs/22.3 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI)

>>>>> On Thu, 22 Dec 2011 12:28:31 +0100, Carsten Mattner <address@hidden> said:

> On Thu, Dec 22, 2011 at 1:42 AM, YAMAMOTO Mitsuharu
> <address@hidden> wrote:
>>>>>>> On Tue, 20 Dec 2011 18:24:07 +0900, YAMAMOTO Mitsuharu
>>>>>>> <address@hidden> said:
>>> Most of the uses of the Carbon framework in the Mac port are for
>>> Apple Events and Carbon Events.
>> The main purpose of the use of them is to avoid Lisp evaluation
>> inside read_socket_hook.

> No way to make that work similarly without Carbon?

As far as I know.  I actually tried that at the very early stage of
the development of the predecessor of the Mac port.

>> I think keeping such a fundamental design principle of Emacs is
>> more important for avoiding unpredictable problems that cannot
>> happen on other platforms, rather than superficially suppressing
>> the use of 64-bit (non-GUI) Carbon, which is widely misunderstood
>> as deprecated.

> I don't follow you here. What's the issue with 64-bit and Carbon?
> Terminal.app looks like it's 64-bit.

No issue at least in a technical sense.  The only issue would be those
who are not familiar with Mac OS X development tend to rant "Carbon is
deprecated!" without knowing the detail or its actual use in many

                                     YAMAMOTO Mitsuharu

reply via email to

[Prev in Thread] Current Thread [Next in Thread]