emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Mariusz Klochowicz <mariusz.klochowicz@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Org parser error in org-ai [9.6.5 (release_9.6.5-3-g2993f4 @ /usr/local/Cellar/emacs-plus@29/29.0.90/share/emacs/29.0.90/lisp/org/)]
Date: Fri, 30 Jun 2023 12:17:25 +0000	[thread overview]
Message-ID: <87v8f5p2ju.fsf@localhost> (raw)
In-Reply-To: <708F85C7-6769-4C16-9C47-7B620A9682B2@gmail.com>

Mariusz Klochowicz <mariusz.klochowicz@gmail.com> writes:

> org-ai buffer encountered a bug during execution, whilst populating the answer from `org-ai-explain-code`.
>
>
> Here's the log: 
>
> ⛔ Warning (org-element-cache): org-element--cache: Org parser error in *org-ai-on-region*::2885. Resetting.
> The error was: (error "Invalid search bound (wrong side of point)")
> Backtrace:
> "  backtrace-to-string(nil)
>   org-element-at-point()
>   org-element-context()
>   org-appear--current-elem()
>   org-appear--post-cmd()
> "

Thanks for reporting!
Are you seeing this warning frequently?
If yes, may you set org-element--cache-self-verify to 'backtrace and
then post the long diagnostics data that will additionally appear in the
warnings buffer?

(beware that the diagnostics may contain some buffer text; you may want
to strip sensitive data from there or send it privately).

-- 
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>


      reply	other threads:[~2023-06-30 12:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28  3:33 [BUG] Org parser error in org-ai [9.6.5 (release_9.6.5-3-g2993f4 @ /usr/local/Cellar/emacs-plus@29/29.0.90/share/emacs/29.0.90/lisp/org/)] Mariusz Klochowicz
2023-06-30 12:17 ` Ihor Radchenko [this message]

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=87v8f5p2ju.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=mariusz.klochowicz@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).