emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Alejandro Pérez Carballo" <apcarballo@gmail.com>
To: Ihor Radchenko <yantar92@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: Wed, 23 Feb 2022 17:52:18 -0800	[thread overview]
Message-ID: <C09E2131-4758-45DB-96A7-6AEF158DE240@gmail.com> (raw)
In-Reply-To: <875yp6p3xm.fsf@localhost>

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-to-string(nil)
  self-insert-command(1 34)
  funcall-interactively(self-insert-command 1 34)
  call-interactively(self-insert-command nil nil)



> On Feb 22, 2022, at 9:06 PM, Ihor Radchenko <yantar92@gmail.com> wrote:
> Alejandro Pérez Carballo <apcarballo@gmail.com> writes:
>> I was simply entering an entry to my main bib file. I received an error message and was asked to submit this report.
> Thanks for the report!
> Do I understand correctly that you got:
> 1. An error message
> 2. A warning popup
> Did it happen when you were _not_ in Org buffer and you did not use
> minibuffer completion?
> Do you recall the error/warning text?
> Best,
> Ihor

  reply	other threads:[~2022-02-24  1:53 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 [this message]
2022-02-24 13:39     ` Ihor Radchenko
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:

  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=C09E2131-4758-45DB-96A7-6AEF158DE240@gmail.com \
    --to=apcarballo@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \


* 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


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