From: Nick Roberts <nickrob@snap.net.nz>
Cc: drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: [drew.adams@oracle.com: RE: tooltip-mode disabled prevents messages in minibuffer]
Date: Sun, 23 Jul 2006 11:03:21 +1200 [thread overview]
Message-ID: <17602.44729.127250.330091@kahikatea.snap.net.nz> (raw)
In-Reply-To: <uu05aey4l.fsf@gnu.org>
> > I can't reproduce this on GNU/Linux.
> What do you see on GNU/Linux? Do you see the TTTTTTTTTTTTTTTTT
> message in the echo area?
Yes. It works as expected
> Also, what is your Emacs configuration? (The toolkit, if any, is the
> most interesting detail.)
GNU Emacs 22.0.50.42 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
> > I don't think so. The item TEST has no help-echo. Messages disappear
> > when Emacs receives further input.
>
> This is not entirely accurate, see below: no help-echo causes Emacs to
> clear the echo area, probably to erase the previous help-echo.
I see I was wrong now. No help-echo must clear the echo area otherwise
the old help text would remain visible while over a new menu item.
> Anyway, I looked into the code, compared the X version with the w32
> version, and frankly, I'm baffled.
>
> Here's what I see in the code: if a menu item doesn't have an
> associated help-echo string, both X and w32 versions call
> kbd_buffer_store_help_event with nil as its second argument. (For the
> w32 version, see w32menu.c:w32menu_display_help; for the X version,
> see xmenu.c:menu_highlight_callback.) This nil eventually winds up in
> keyboard.c:show_help_echo, which explicitly calls message(0) if its
> HELP argument is nil. The call message(0) should clear the echo area,
> AFAIU.
>
> In the w32 version, if I put a breakpoint inside show_help_echo, it
> breaks after I click on TEST in the menu. If I then step through the
> function, I clearly see the TTTTTTTTTTTTTTTTT message in the echo area
> until Emacs calls message(0), at which point the echo area is cleared.
>
> I don't have access to a GUI version of Emacs on GNU/Linux where I'm
> typing this--could someone please see which part of the above
> description works differently on GNU/Linux, and why?
If I put a breakpoint inside show_help_echo and click C-down-mouse-2 the
window manager freezes. If I instrument the function test with edebug
and step through it, the message doesn't appear. The problem with debugging
these situations is that it changes the behaviour.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-07-22 23:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 4:38 [drew.adams@oracle.com: RE: tooltip-mode disabled prevents messages in minibuffer] Richard Stallman
2006-07-22 5:39 ` Nick Roberts
2006-07-22 10:23 ` Eli Zaretskii
2006-07-22 23:03 ` Nick Roberts [this message]
2006-07-23 3:21 ` Eli Zaretskii
2006-07-23 7:28 ` Eli Zaretskii
2006-07-23 11:18 ` Nick Roberts
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=17602.44729.127250.330091@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@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).