From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: help-echo in Custom
Date: Fri, 15 Aug 2003 09:40:17 -0500 (CDT) [thread overview]
Message-ID: <200308151440.h7FEeHf01531@raven.dms.auburn.edu> (raw)
In-Reply-To: <rj4r0j87fc.fsf@zuse.dina.kvl.dk> (message from Per Abrahamsen on Fri, 15 Aug 2003 13:52:07 +0200)
Per Abrahamsen wrote:
The correct solution would probably be for the code to carefully
translate the argument to :help-echo into the format expected by
help-echo, probably by creating a helper function on the fly.
Actually, that appears to be exactly what is done. What confused me
was that the Elisp manual suggests that the rules for correct
arguments to :help-echo are exactly the same as for 'help-echo values.
I have no problem with them actually being different, as long as that
would be clearly mentioned in the Elisp manual. The usual arguments
to 'help-echo make indeed no sense in the case of widgets.
The only change I suggest (apart from the change in the Elisp manual)
is to allow expressions that evaluate to strings in :help-echo, as
they are for `help-echo values. This is easy to do by making the
minor change in `widget-echo-help' I suggested. Otherwise, authors
who only check their code using mouse-over are going to believe such
arguments work anyway, whereas with the present version of
`widget-echo-help', they do not work with <tab>.
Sincerely,
Luc.
next prev parent reply other threads:[~2003-08-15 14:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-14 16:46 help-echo in Custom Luc Teirlinck
2003-08-14 17:25 ` Luc Teirlinck
2003-08-14 18:14 ` Luc Teirlinck
2003-08-14 19:00 ` Luc Teirlinck
2003-08-14 19:32 ` Luc Teirlinck
2003-08-14 19:56 ` Luc Teirlinck
2003-08-15 11:52 ` Per Abrahamsen
2003-08-15 14:40 ` Luc Teirlinck [this message]
2003-08-17 0:36 ` Richard Stallman
2003-08-17 5:00 ` Luc Teirlinck
-- strict thread matches above, loose matches on Subject: below --
2003-08-14 16:56 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=200308151440.h7FEeHf01531@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--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.