From: Yuri Khan <yuri.v.khan@gmail.com>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Why does show_help_echo call substitute_command_keys?
Date: Fri, 21 Jul 2017 15:48:13 +0700 [thread overview]
Message-ID: <CAP_d_8X2H0tb6JVST9=_hUfQtJ9iLU7b31gVycXu9Nt6xL_2Fw@mail.gmail.com> (raw)
In-Reply-To: <4f821efa-1448-8ba0-d164-abeff36180d4@gmail.com>
On Fri, Jul 21, 2017 at 12:05 AM, Clément Pit-Claudel
<cpitclaudel@gmail.com> wrote:
> Hi emacs-devel,
>
> I'm puzzled by this bit of code in show_help_echo:
>
> if (STRINGP (help) || NILP (help))
> {
> if (!NILP (Vshow_help_function))
> call1 (Vshow_help_function, Fsubstitute_command_keys (help));
> help_echo_showing_p = STRINGP (help);
> }
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?
> This is causing trouble in Flycheck, because we set help-echo properties on error spans and we expect them to be displayed without modifications when users hover over them. Is there a way to disable command-key- (and quote-) substitution in help-echo strings?
There should probably be a function that knows when and how to quote
the characters that cause such substitution with \=.
next prev parent reply other threads:[~2017-07-21 8:48 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 [this message]
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
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_8X2H0tb6JVST9=_hUfQtJ9iLU7b31gVycXu9Nt6xL_2Fw@mail.gmail.com' \
--to=yuri.v.khan@gmail.com \
--cc=cpitclaudel@gmail.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).