[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Pretest next week
From: |
YAMAMOTO Mitsuharu |
Subject: |
Re: Pretest next week |
Date: |
Thu, 05 Mar 2009 09:56:01 +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 Sat, 31 Jan 2009 16:35:27 +0900, YAMAMOTO Mitsuharu <address@hidden>
>>>>> said:
>>>>> On Sat, 31 Jan 2009 01:44:22 -0500, Richard M Stallman <address@hidden>
>>>>> said:
>> If fixing this will require major changes, that may be a reason to
>> delay the pretest -- if someone is willing to working on these
>> major changes right away.
> In the platforms other than the Cocoa/GNUstep port, menu bar is
> uniformly activated by the x_activate_menubar call in
> kbd_buffer_get_event, which is called from read_char. However, the
> Cocoa/GNUstep port activates the menu bar and starts mouse tracking
> in the context of read_socket_hook, which is supposed to be called
> from fairly random states of the Lisp interpreter. (That port
> currently calls read_socket_hook only from limited locations, and
> that makes this problem obscured and the C-g handling improper.)
Correction: bug #2564 shows that even "read_socket_hook only from
limited locations" is problematic. In the reported case,
read_socket_hook is called from the select (ns_select, actually) call
in wait_reading_process_output, and a menu bar activation there leads
to Lisp evaluation containing Faccept_process_output.
YAMAMOTO Mitsuharu
address@hidden
- Re: Pretest next week,
YAMAMOTO Mitsuharu <=