From: Ihor Radchenko <yantar92@posteo.net>
To: Robert Place <robert.place@alldyn.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Backtrace from orh-element-cache failing in when editing non-org file [9.6.15 (release_9.6.15 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)]
Date: Sat, 12 Oct 2024 12:05:10 +0000 [thread overview]
Message-ID: <87ed4lsf0p.fsf@localhost> (raw)
In-Reply-To: <m234l95man.fsf@gmail.com>
Robert Place <robert.place@alldyn.com> writes:
> This issue occurred while editing the init.el, I was testing out the
> detangle functionality for the target file that was generated
> through org-babel-tangle. It is unclear why this warning appeared but
> the auto-completion via company still appears to work just fine.
>
> Emacs : GNU Emacs 29.2 (build 1, aarch64-apple-darwin21.6.0, NS appkit-2113.60 Version 12.6.6 (Build 21G646))
> of 2024-01-18
> Package: Org mode version 9.6.15 (release_9.6.15 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)
Thanks for reporting!
It is hard to judge what happened without seeing the actual backtrace,
but I note that you are not using the latest released version of Org
mode.
May you upgrade to the latest Org mode from ELPA and let me know if the
problem is still present?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-10-12 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 14:38 [BUG] Backtrace from orh-element-cache failing in when editing non-org file [9.6.15 (release_9.6.15 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)] Robert Place
2024-10-12 12:05 ` Ihor Radchenko [this message]
[not found] ` <m2sesy9zrj.fsf@alldyn.com>
2024-10-15 18:13 ` Ihor Radchenko
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=87ed4lsf0p.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=robert.place@alldyn.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).