From: Manuel Uberti <manuel.uberti@inventati.org>
To: eliz@gnu.org, 38633@debbugs.gnu.org
Subject: bug#38633: 27.0.50; Broken faces
Date: Mon, 16 Dec 2019 08:56:33 +0100 [thread overview]
Message-ID: <63e09a63-012c-f598-128e-8400793eae53@inventati.org> (raw)
In-Reply-To: <E25D90A2-9A77-4B49-B235-2ADA7E9CF1FA@gnu.org>
On 16/12/19 08:48, Eli Zaretskii wrote:
> Are you saying that the problems were caused by dd3f2130cf2 alone? IOW, if you go back to d57bb0c323 (note: this is NOT the parent of dd3f2130cf2!), then the problems disappear?
Thank you for the prompt reply. Using d57bb0c323 the problem disappears.
> In general, I don't understand what exactly is the face setup in your scenario (I don't use helm), even afyer reading the issue you referred to. So I will need a detailed description of what happens in that use case, including whether there are display strings or overlays involved, and what are the faces in effect there. For best results, please provide a reproduction recipe starting from "emacs -Q", preferably not involving helm at all.
It's hard for me to provide a recipe without Helm, because I only noticed the
problem within Helm. The Helm face involved here appears to be `helm-source-header`.
Helm repository contains a script (`emacs-helm.sh`), which when will give you a
clean Emacs session from `emacs -Q` with only Helm enabled.
Kind regards
--
Manuel Uberti
next prev parent reply other threads:[~2019-12-16 7:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 7:04 bug#38633: 27.0.50; Broken faces Manuel Uberti
2019-12-16 7:48 ` Eli Zaretskii
2019-12-16 7:56 ` Manuel Uberti [this message]
2019-12-16 8:07 ` Eli Zaretskii
2019-12-16 8:15 ` Manuel Uberti
2019-12-16 8:46 ` Eli Zaretskii
2019-12-16 9:02 ` Manuel Uberti
2019-12-16 11:19 ` Eli Zaretskii
2019-12-16 11:29 ` Manuel Uberti
2019-12-16 15:46 ` Eli Zaretskii
2019-12-16 15:45 ` 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
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=63e09a63-012c-f598-128e-8400793eae53@inventati.org \
--to=manuel.uberti@inventati.org \
--cc=38633@debbugs.gnu.org \
--cc=eliz@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).