From: Yuri Khan <yuri.v.khan@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: "Clément Pit-Claudel" <cpitclaudel@gmail.com>,
"Emacs developers" <emacs-devel@gnu.org>
Subject: Re: Why does show_help_echo call substitute_command_keys?
Date: Sat, 22 Jul 2017 00:49:00 +0700 [thread overview]
Message-ID: <CAP_d_8XL3r5_zAekSQSrESDVa51kMZjE8a9LMhocB9iF9yRuQA@mail.gmail.com> (raw)
In-Reply-To: <6364429e-0696-4835-bed8-458a6095067f@default>
On Fri, Jul 21, 2017 at 9:54 PM, Drew Adams <drew.adams@oracle.com> wrote:
>> Because the help-echo property is the Emacs API to tooltips, and
>> tooltips are expected to be able to display keyboard equivalents
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> to clicking the thing that is pointed?
>
> A tooltip should just display whatever text it is handed,
> with no fiddling with or elaboration of that text. If you
> need such fiddling, whether by ``substitute-command-keys'
> or `format' or something else, do it beforehand.
Actually, client code that wishes to display a command key in a
tooltip can set the help-echo property to a function. So, hardcoding
the substitute-command-keys call in show_help_echo does not seem
necessary after all.
next prev parent reply other threads:[~2017-07-21 17:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 17:05 Why does show_help_echo call substitute_command_keys? Clément Pit-Claudel
2017-07-21 8:48 ` Yuri Khan
2017-07-21 9:01 ` Clément Pit-Claudel
2017-07-21 9:10 ` Yuri Khan
2017-07-21 9:19 ` Clément Pit-Claudel
2017-07-21 13:43 ` Stefan Monnier
2017-07-21 14:54 ` Drew Adams
2017-07-21 14:54 ` Drew Adams
2017-07-21 14:54 ` Drew Adams
2017-07-21 14:54 ` Drew Adams
2017-07-21 17:49 ` Yuri Khan [this message]
2017-07-21 17:54 ` Clément Pit-Claudel
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=CAP_d_8XL3r5_zAekSQSrESDVa51kMZjE8a9LMhocB9iF9yRuQA@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=cpitclaudel@gmail.com \
--cc=drew.adams@oracle.com \
--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).