emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Justin Abrahms" <justin@abrah.ms>
To: "Ihor Radchenko" <yantar92@gmail.com>
Cc: "Karol Wójcik via General discussions about Org-mode."
	<emacs-orgmode@gnu.org>
Subject: Re: [BUG] incorrect cached element under native-comp [9.5.4 (9.5.4-ga8b322 @ /Users/jabrahms/.emacs.d/straight/build/org/)]
Date: Tue, 14 Jun 2022 00:04:45 -0700	[thread overview]
Message-ID: <d01e30a4-628c-4685-b1af-372f093dfbf2@www.fastmail.com> (raw)
In-Reply-To: <878rpzhgrj.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 678 bytes --]

All of that is correct, yes.

On Mon, Jun 13, 2022, at 11:59 PM, Ihor Radchenko wrote:
> "Justin Abrahms" <justin@abrah.ms> writes:
> 
> > I saw this error when opening emacs.org via (counsel-find-file &optional INITIAL-INPUT INITIAL-DIRECTORY)
> >
> > Slightly different error now (same style, different element), but I didn't get a backtrace.
> >
> > https://gist.github.com/justinabrahms/4bc97379cb8d8e317ca98a1f09524a5c
> 
> Do you mean that you did the following:
> 
> 1. (setq org-element--cache-self-verify 'backtrace)
> 2. (setq org-element--cache-self-verify-frequency 1.0)
> 3. Open emacs.org using counsel-find-file
> 4. Got the above backtrace?
> 
> Best,
> Ihor
> 

[-- Attachment #2: Type: text/html, Size: 1293 bytes --]

  reply	other threads:[~2022-06-14  7:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-12 18:37 [BUG] incorrect cached element under native-comp [9.5.4 (9.5.4-ga8b322 @ /Users/jabrahms/.emacs.d/straight/build/org/)] Justin Abrahms
2022-06-14  5:03 ` Ihor Radchenko
2022-06-14  6:06   ` Justin Abrahms
2022-06-14  6:59     ` Ihor Radchenko
2022-06-14  7:04       ` Justin Abrahms [this message]
2022-06-14  7:20         ` Ihor Radchenko
2022-06-25 15:46           ` Justin Abrahms

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=d01e30a4-628c-4685-b1af-372f093dfbf2@www.fastmail.com \
    --to=justin@abrah.ms \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@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).