-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Faces inconsistency #55
Comments
This is related to emacs-helm/helm#2213 and there is a long standing thread on emacs-dev about this (one of the issues that prevent emacs-27 starting pretest). |
That annoy everybody... |
I see, thanks for the tip. I tried adding |
That function doesn't seems to fix the problem though. |
Manuel Uberti <notifications@github.com> writes:
That function doesn't seems to fix the problem though.
Hmm, perhaps :extend code have changed in emacs-27, I will try to update
ASAP to try. I am actually on 7e387c9e526.
Perhaps your theme is affected as well (most themes are actually).
…--
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997
|
Indeed, I installed a fresh emacs-27 and many faces are broken now with the last changes in the |
Thank you for taking the time to look into this. I opened a bug here referring to this ticket. |
See emacs-helm/helm#2213 for more details. |
Thanks to your recipe, I think Eli found the problem: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38633#44 |
This now appears to be fixed by commit I'm closing this issue, then. Thanks again for helping me debug it. |
I confirm it is now working fine, thanks. |
Hi,
I am using latest
helm
andhelm-ls-git
(I cloned the repositories withstraight
, so nopackage.el
involved).Starting from
emacs -Q
, I installedhelm
andhelm-ls-git
(again, usingstraight
).M-x helm-browse-project
gives me this:While
helm-M-x
gives me this:I was expecting to see
Buffers in git project (master)
andGit files (master)
with a similar (the same?) face asEmacs Commands History
andEmacs Commands
.This is the Emacs version I am using:
If you need me to provide more details and/or do further tests, feel free to ask.
The text was updated successfully, but these errors were encountered: