From: Ihor Radchenko <yantar92@gmail.com>
To: "Alejandro Pérez Carballo" <apcarballo@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Prompted to submit (unsure what happened) [9.5.2 (9.5.2-g072523 @ /Users/apc/.emacs.d/straight/build/org/)]
Date: Thu, 24 Feb 2022 21:39:57 +0800 [thread overview]
Message-ID: <87o82wo02a.fsf@localhost> (raw)
In-Reply-To: <C09E2131-4758-45DB-96A7-6AEF158DE240@gmail.com>
Alejandro Pérez Carballo <apcarballo@gmail.com> writes:
> Sorry about the unclear report. I was indeed _not_ in an org buffer. I do not think I was using minibuffer completion, but I cannot remember. I now just got a similar error message, this time when working on an Elisp buffer. The error message says:
>
> Warning (org-element-cache): org-element--cache: Org parser error in setup-biblio.el::5918. Resetting.
> The error was: (error "rx ‘**’ range error")
> Backtrace:
> " backtrace-to-string(nil)
> org-element-at-point()
> org-in-src-block-p()
> run-hook-with-args-until-success(org-in-src-block-p)
> electric-quote-post-self-insert-function()
> self-insert-command(1 34)
> funcall-interactively(self-insert-command 1 34)
> call-interactively(self-insert-command nil nil)
> command-execute(self-insert-command)
> "
Thanks for the backtrace! It is very clear that something in
electric-quote-mode-hook (or maybe in electric-quote-inhibit-functions)
is calling org-in-src-block-p.
org-in-src-block-p does not work outside Org mode. It used to (at least,
it did not throw an error), but it is not the case anymore and it was
never guaranteed that Org functions can reliably work outside Org mode.
I do not see explicit customisation adding org-in-src-block-p in your
config from the first email. I presume that some third-party package is
adding org-in-src-block-p to electric-quote-mode. I would first try to
check the values of electric-quote-inhibit-functions and
electric-quote-mode-hook and check if they contain org-* staff. Then, I
would bisect the config to find out which package is doing it. What you
are seeing is a bug in that package and should be reported.
Best,
Ihor
next prev parent reply other threads:[~2022-02-24 13:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 20:55 [BUG] Prompted to submit (unsure what happened) [9.5.2 (9.5.2-g072523 @ /Users/apc/.emacs.d/straight/build/org/)] Alejandro Pérez Carballo
2022-02-23 5:06 ` Ihor Radchenko
2022-02-24 1:52 ` Alejandro Pérez Carballo
2022-02-24 13:39 ` Ihor Radchenko [this message]
2022-02-24 19:27 ` Alejandro Pérez Carballo
2022-02-24 22:48 ` Alejandro Pérez Carballo
2022-02-26 7:23 ` 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=87o82wo02a.fsf@localhost \
--to=yantar92@gmail.com \
--cc=apcarballo@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).