From: Samuel Wales <samologist@gmail.com>
To: No Wayman <iarchivedmywholelife@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: [PATCH] org-agenda: "Invalid face reference: t" errors [9.4 (release_9.4-49-g4b150d @ /home/n/.emacs.d/straight/build/org/)]
Date: Tue, 6 Oct 2020 14:38:37 -0700 [thread overview]
Message-ID: <CAJcAo8utewaM9ZXDAbJjh95fknnXgC7tbGzLebEEpkshmSW6cg@mail.gmail.com> (raw)
In-Reply-To: <87v9fnc3if.fsf@gmail.com>
i can confirm these errors in maint [didn't confirm the patch or
workaround]. thanks for debugging what i could not.
On 10/5/20, No Wayman <iarchivedmywholelife@gmail.com> wrote:
>
> I noticed recently that my message buffer was getting clobbered
> with thousands of Invalid face reference errors when moving point
> around an org-agenda buffer. e.g.:
>
>> Invalid face reference: t [4519 times]
>
> Git bisect points to commit
> 7a12e149907b5921011710d869b7554c35859c89
>
>> org.el (org-display-outline-path): Fix faces of the message
>>
>> * lisp/org.el (org-display-outline-path): Set :height as the
>> default face height, and don't change other face attributes.
>>
>> See a3576543f for a previous fix, and this discussion:
>> <https://orgmode.org/list/21ef0e94-e766-455c-a45c-fe30e316c121@Spark>
>
> As a workaround, setting `org-agenda-show-outline-path' to nil
> prevents the errors.
> I believe the face spec in the call to `add-face-text-property' in
> `org-display-outline-path' is incorrect.
> The attached patch replaces it with an anonymous face, which works
> on my end.
>
>
--
The Kafka Pandemic
Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
next prev parent reply other threads:[~2020-10-06 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 5:44 Bug: [PATCH] org-agenda: "Invalid face reference: t" errors [9.4 (release_9.4-49-g4b150d @ /home/n/.emacs.d/straight/build/org/)] No Wayman
2020-10-06 21:38 ` Samuel Wales [this message]
2020-10-07 4:50 ` Kyle Meyer
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJcAo8utewaM9ZXDAbJjh95fknnXgC7tbGzLebEEpkshmSW6cg@mail.gmail.com \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=iarchivedmywholelife@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).