all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Manuel Uberti <manuel.uberti@inventati.org>
To: eliz@gnu.org, 38633@debbugs.gnu.org
Cc: spacibba@aol.com
Subject: bug#38633: 27.0.50; Broken faces
Date: Mon, 16 Dec 2019 09:15:44 +0100	[thread overview]
Message-ID: <e9309d36-e5f4-7aea-cc0a-d2cc7a1e84b2@inventati.org> (raw)
In-Reply-To: <821D3B73-244C-447A-B3DB-80BFCE709EC8@gnu.org>

On 16/12/19 09:07, Eli Zaretskii wrote:
> If a standalone recipe cannot be provided, debugging this problem will be difficult for me.  Perhaps Jimmy (CC'd) will be able to look into this.

Again, I only noticed the problem within Helm, so I can only give a you a
minimal recipe from within it.

If you clone the Helm repository and run `emacs-helm.sh`, you can:

- M-x helm-find-files RET (note the "Find files (C-l: go up one level" header face)
- M-x helm-M-x RET (note the "Emacs Commands" header face

You will then see the differences I posted here:
https://github.com/emacs-helm/helm-ls-git/issues/55#issuecomment-565710173

> Can you at least show the results of "M-x describe-text-properties RET" at the problematic position?
> 

AFAIK I cannot place point on a Helm source header, so I cannot run `M-x
describe-text-properties` on it.

-- 
Manuel Uberti





  reply	other threads:[~2019-12-16  8:15 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
2019-12-16  8:07     ` Eli Zaretskii
2019-12-16  8:15       ` Manuel Uberti [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e9309d36-e5f4-7aea-cc0a-d2cc7a1e84b2@inventati.org \
    --to=manuel.uberti@inventati.org \
    --cc=38633@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=spacibba@aol.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.