From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Reducing mouse-dependency In Emacs.
Date: Wed, 13 Aug 2003 19:35:29 -0500 (CDT) [thread overview]
Message-ID: <200308140035.h7E0ZTf26665@raven.dms.auburn.edu> (raw)
In-Reply-To: <16186.49695.437995.793551@nick.uklinux.net> (message from Nick Roberts on Wed, 13 Aug 2003 23:56:31 +0100)
Nick Roberts wrote:
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.
If you, or anybody else, can point me to an existing Lisp function or
any other way that Emacs already "provides" these arguments in Lisp
and without mouse-over, I obviously will use it (and then everything I
write below can just be ignored). I could not find any, but I did not
read through the entire Emacs Lisp code.
I do not even really believe that Miles was necessarily arguing
against my proposed new primitive (he can tell), I believe he was just
asking me for information.
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.
Did you check in detail how Custom manages to print the help-echo in
the echo area? If I understood correctly (it does not at all seem
that "simple" to me), it apparently uses two extra text properties it
manages itself, `button' and `field', depending on the situation, to
store and recover the information.
I propose to use one extremely simple and short C function and one
very simple and short Lisp function, compared to the entire machinery
used by Custom, and it would work in a way more general situation. In
my situation, I can not do what Custom does, because I do not have the
information stored in `button' and `field' properties.
Sincerely,
Luc.
next prev parent reply other threads:[~2003-08-14 0:35 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
2003-08-14 0:35 ` Luc Teirlinck [this message]
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=200308140035.h7E0ZTf26665@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.