From: Nick Roberts <nick@nick.uklinux.net>
Cc: emacs-devel@gnu.org
Subject: Re: Reducing mouse-dependency In Emacs.
Date: Wed, 13 Aug 2003 23:56:31 +0100 [thread overview]
Message-ID: <16186.49695.437995.793551@nick.uklinux.net> (raw)
In-Reply-To: <200308131259.h7DCxbI22580@raven.dms.auburn.edu>
Luc Teirlinck writes:
>
> Miles Bader wrote:
>
> Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> > To take care of functional values, I need not only the value of the
> > property but also need to know whether it was found in an overlay (and
> > if so which overlay) or as a text property.
>
> How come?
>
> Because:
>
> If the value of the `help-echo' property is a function, that
> function is called with three arguments, WINDOW, OBJECT and
> POSITION and should return a help string or NIL for none. The
> first argument, WINDOW is the window in which the help was found.
> The second, OBJECT, is the buffer, overlay or string which had
> the
> `help-echo' property. The POSITION argument is as follows...
I must admit I've lost the plot but it seems to have got far too complicated.
I agree with Miles, I don't think that you need to know all these
things. I think that Emacs *provides* the appropriate arguments depending on
the context, which can then used in the function that evaluates to a string.
I'm always in favour of re-use to keep things simple and, IMO, `customize'
works well with and without the mouse. Here, a tooltip is displayed if the
mouse is placed over a widget. In the mouseless scenario, the help is
displayed in the echo area. However, this doesn't happen when point is over a
widget but when the user types <tab> (widget-forward) or <S-tab>
(widget-backward). This is less distracting and fits well with earlier
comments about emacspeak. Could you not do something similar with
next-help-echo-region and previous-help-echo-region?
Nick
next prev parent reply other threads:[~2003-08-13 22:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 5:36 Reducing mouse-dependency In Emacs Luc Teirlinck
2003-08-13 7:47 ` Miles Bader
2003-08-13 12:59 ` Luc Teirlinck
2003-08-13 22:56 ` Nick Roberts [this message]
2003-08-14 0:35 ` Luc Teirlinck
2003-08-14 1:42 ` Miles Bader
2003-08-14 1:04 ` Luc Teirlinck
2003-08-13 14:32 ` Luc Teirlinck
-- strict thread matches above, loose matches on Subject: below --
2003-08-12 2:49 Luc Teirlinck
2003-08-12 1:29 Luc Teirlinck
2003-08-12 1:43 ` Luc Teirlinck
2003-08-10 3:42 Luc Teirlinck
2003-08-10 6:08 ` Eli Zaretskii
2003-08-10 14:53 ` Luc Teirlinck
2003-08-11 12:53 ` Richard Stallman
2003-08-10 16:50 ` Stefan Monnier
2003-08-10 23:09 ` Luc Teirlinck
2003-08-11 4:05 ` Luc Teirlinck
2003-08-11 23:16 ` Richard Stallman
2003-08-11 6:04 ` Eli Zaretskii
2003-08-11 15:52 ` Luc Teirlinck
2003-08-11 17:52 ` Eli Zaretskii
2003-08-11 14:54 ` Stefan Monnier
2003-08-12 2:30 ` Luc Teirlinck
2003-08-12 6:28 ` Eli Zaretskii
2003-08-12 16:08 ` Luc Teirlinck
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16186.49695.437995.793551@nick.uklinux.net \
--to=nick@nick.uklinux.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.