From: Eli Zaretskii <eliz@gnu.org>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: 23246@debbugs.gnu.org
Subject: bug#23246: 25.0.92; Local face-remapping-alist doesn't affect tooltips
Date: Sat, 09 Apr 2016 12:35:00 +0300 [thread overview]
Message-ID: <83oa9ji0qj.fsf@gnu.org> (raw)
In-Reply-To: <87k2k7c1cm.fsf@gmail.com> (message from Artur Malabarba on Fri, 08 Apr 2016 17:06:01 -0300)
> From: Artur Malabarba <bruce.connor.am@gmail.com>
> Cc: 23246@debbugs.gnu.org
> Date: Fri, 08 Apr 2016 17:06:01 -0300
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Why did you expect them to be blue? Tooltips are special frames that
> > don't display any buffer, whereas face-remap-add-relative is
> > documented as affecting only the buffer that was current at the time
> > it was called.
>
> Sorry, to me it wasn't obvious that tooltips are different frames.
I've added to the ELisp manual some documentation about that, which
makes it clear these are frames.
> I want to change the way tooltips are displayed in a major-mode I'm
> writing. I don't want to change this face globally for the user, only
> change it in the buffers where this major-mode is active.
>
> I understand that might not be possible, in which case feel free to
> close.
I think you can achieve that by putting your own hook function on the
tooltip-functions list.
Let me know if there's anything else to do about this bug report.
next prev parent reply other threads:[~2016-04-09 9:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 19:22 bug#23246: 25.0.92; Local face-remapping-alist doesn't affect tooltips Artur Malabarba
2016-04-08 19:34 ` Eli Zaretskii
2016-04-08 20:06 ` Artur Malabarba
2016-04-09 9:04 ` martin rudalics
2016-04-09 9:35 ` Eli Zaretskii [this message]
2016-04-09 12:50 ` martin rudalics
2016-04-09 13:18 ` Eli Zaretskii
2016-04-11 3:15 ` Artur Malabarba
2016-04-11 15:40 ` Eli Zaretskii
2016-04-12 7:30 ` martin rudalics
2016-04-12 14:26 ` Drew Adams
2016-04-12 15:14 ` Eli Zaretskii
2016-04-09 9:04 ` martin rudalics
2016-04-09 9:39 ` Eli Zaretskii
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=83oa9ji0qj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23246@debbugs.gnu.org \
--cc=bruce.connor.am@gmail.com \
/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.