unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: Documentation for GUD tooltips
Date: Fri, 11 Mar 2005 21:30:12 +1300	[thread overview]
Message-ID: <16945.22292.587023.301222@farnswood.snap.net.nz> (raw)
In-Reply-To: <E1D9ZGb-0004F9-LD@fencepost.gnu.org>

 >     Its a bit more subtle than that. GUD tooltips use track-mouse (ordinary
 >     tooltips work at a lower level and don't rely on events in lisp).  For
 >     a GUD tooltip to work, the lisp-level mouse-movement event must be
 >     generated in the buffer with the overlay arrow and the mode of the
 >     selected buffer must belong to tooltip-gud-modes.  Note that the
 >     mouse-movement need not occur in the selected buffer.  The list
 >     `tooltip-gud-modes' includes gud-mode so that the user may move the
 >     mouse over a variable in the buffer of the source while the GUD buffer
 >     remains selected.
 > 
 > Why was it made to depend on the selected buffer?  Why implement such
 > bizarre behavior?  I think that counts as a bug; can we fix it?

Maybe it is a bug but no-one has complained about it, probably because not
many people use GUD tooltips. The comments in tooltip.el suggest that this is
a kludge to avoid display problems (Gerd Moellmann?), so I'm not sure that
there is an easy fix. There are other problems that I would like to fix such
as the fact that if GUD tooltips display in the echo area then so must
ordinary tooltips, but these are not showstoppers. Surely solving these
problems should wait till after the release?

Nick

  reply	other threads:[~2005-03-11  8:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16943.51590.58792.371431@farnswood.snap.net.nz>
2005-03-11  1:48 ` Documentation for GUD tooltips Richard Stallman
2005-03-11  8:30   ` Nick Roberts [this message]
2005-03-12 22:16     ` Richard Stallman

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=16945.22292.587023.301222@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --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).