unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: jasonr@gnu.org, emacs-devel@gnu.org
Subject: Re: tooltip-use-echo-area disappeared
Date: Tue, 14 Jun 2005 23:35:05 +0200	[thread overview]
Message-ID: <umzps62ra.fsf@gnu.org> (raw)
In-Reply-To: <17070.23884.564148.959259@farnswood.snap.net.nz> (message from Nick Roberts on Tue, 14 Jun 2005 16:30:04 +1200)

> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Tue, 14 Jun 2005 16:30:04 +1200
> Cc: emacs-devel@gnu.org, Jason Rumney <jasonr@gnu.org>
> 
> Resurrecting tooltip-use-echo-area is unrelated to making the tty version
> support tooltips.

IMO, it is related.

> It was just a flag that re-directed the output of tooltip-show-help
> to the echo area i.e. in the case of normal tooltips back to where
> it was displayed before tooltips were turned on.

If you mean to say that turning tooltips off would still display the
tooltip text in the echo area, then I agree with Jason: that's a bug
that should be fixed.  It should be possible to have 1 of 3 situations
wrt tooltips:

  (1) no tooltips and no messages in echo area
  (2) tooltip text is displayed in the echo area
  (3) tooltips are displayed as small floating windows

> Normal tooltips and GUD tooltips have quite different internals and 
> putting their associated code in separate files was much more modular.
> Previously if tooltip-use-echo-area was set to t so that normal tooltips
> displayed there, then GUD tooltips would display there.

Internals aside, from the user's point of view, if I want tooltip text
to be displayed in the echo area, I want ALL tooltips to behave like
that.  Why in the world would I like these two variants of tips to
behave differently?

  reply	other threads:[~2005-06-14 21:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02  8:09 tooltip-use-echo-area disappeared Jason Rumney
2005-06-02  9:25 ` Nick Roberts
2005-06-02 12:24   ` jasonr
2005-06-02 13:00     ` Nick Roberts
2005-06-13 12:38       ` Jason Rumney
2005-06-13 14:17         ` Kim F. Storm
2005-06-13 21:03         ` Nick Roberts
2005-06-13 21:54           ` Jason Rumney
2005-06-14  1:11             ` Nick Roberts
2005-06-14  4:38             ` Eli Zaretskii
2005-06-14  4:30               ` Nick Roberts
2005-06-14 21:35                 ` Eli Zaretskii [this message]
2005-06-14 21:33                   ` Nick Roberts
2005-06-15  3:29                     ` Eli Zaretskii
2005-06-16  4:06                     ` Richard Stallman
2005-06-16  9:16                       ` Nick Roberts
2005-06-17  4:38                         ` Richard Stallman
2005-06-17  5:07                           ` Nick Roberts
2005-06-17 10:35                             ` Eli Zaretskii
2005-06-18  8:29                               ` Nick Roberts
2005-06-18 11:16                                 ` Eli Zaretskii
2005-06-17 18:45                             ` Richard Stallman
2005-06-18  8:42                               ` Nick Roberts
2005-06-19  3:51                                 ` Richard Stallman
2005-06-19  4:50                                   ` Nick Roberts
2005-06-16  6:48                     ` Jason Rumney

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=umzps62ra.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@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).