unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Tak Ota <Takaaki.Ota@am.sony.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: table cell menu does not appear at the menubar
Date: Tue, 22 May 2007 00:36:24 +0200	[thread overview]
Message-ID: <46521EE8.7050106@gmail.com> (raw)
In-Reply-To: <20070521.135322.160705042.Takaaki.Ota@am.sony.com>

I have no idea about that, but the problem I mentioned earlier with 
menus on w32 is a race  problem/sync problem (or whatever the correct 
term is).

It might be difficult to catch such problems with the debugger of 
course. I inserted trace output to the console to catch it.


Tak Ota wrote:
> Since I freshly got the completely source from CVS Friday (05/18/07) I
> have built it and been running it under GDB.  So far I haven't seen
> the problem yet.  Has anyone changed something that might have fixed
> this stuck menu problem?
> 
> -Tak
> 
> Fri, 18 May 2007 19:08:57 -0400: Richard Stallman <rms@gnu.org> wrote:
> 
>>     2. When the problem once starts menubar contents do not change
>>        regardless of the mode where point is at.  The last menubar content
>>        is stuck.  The last remaining menu responds to mouse event and
>>        functions correctly.
>>
>> menu_bar_items is the function that is supposed to make a list of
>> all the keymaps to be processed.  So the problem is either there
>> or in or within a function that calls it.
>>
>> When the problem happens, can you see if and when menu_bar_items
>> gets called?  And when it calls get_local_map, what args does it use
>> and what value does it get?

  reply	other threads:[~2007-05-21 22:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-03  0:22 table cell menu does not appear at the menubar Tak Ota
2007-05-03 14:40 ` Stephen Berman
2007-05-03 23:56 ` Richard Stallman
2007-05-04  0:18   ` Tak Ota
2007-05-06 22:26     ` Richard Stallman
2007-05-17 22:21       ` Tak Ota
2007-05-17 22:35         ` Lennart Borgman (gmail)
2007-05-18 14:50           ` Eli Zaretskii
2007-05-18 14:55             ` Lennart Borgman (gmail)
2007-05-18 15:25               ` Eli Zaretskii
2007-05-18 17:54                 ` Lennart Borgman (gmail)
2007-05-18 15:36             ` Jason Rumney
2007-05-18 17:45               ` Lennart Borgman (gmail)
2007-05-18 23:08         ` Richard Stallman
2007-05-21 20:53           ` Tak Ota
2007-05-21 22:36             ` Lennart Borgman (gmail) [this message]
2007-05-22  0:31               ` Tak Ota
2007-05-22 14:52             ` Richard Stallman
2007-05-24  2:38               ` Tak Ota
2007-05-28 12:56                 ` martin rudalics
2007-05-29  0:03                   ` Richard Stallman
2007-05-29  6:20                     ` martin rudalics

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46521EE8.7050106@gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=Takaaki.Ota@am.sony.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).