From: Patrick Useldinger <uselpa@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Emacs-orgmode@gnu.org
Subject: Re: [BUG] org-capture, level-2 heading, org-set-tags-command [9.6.6 ( @ /Users/pu/.emacs.d/elpa/org-9.6.6/)]
Date: Sun, 21 May 2023 11:00:00 +0200 [thread overview]
Message-ID: <99975c56-1ecc-b0f7-8b23-fdd3ee59bc27@gmail.com> (raw)
In-Reply-To: <87lehipyan.fsf@localhost>
On 20/05/2023 22:01, Ihor Radchenko wrote:
> You can try to bisect your config to identify which part is triggering
> the problem. See
> https://list.orgmode.org/orgmode/87ee2nlslt.fsf@localhost/ and
> https://github.com/Malabarba/elisp-bug-hunter
>
FWIW, I just got the following message at startup:
---
Warning (org-element-cache): org-element--cache: Org parser error in
WORK.org::84837. Resetting.
The error was: (error "Invalid search bound (wrong side of point)")
Backtrace:
nil
Please report this to Org mode mailing list (M-x
org-submit-bug-report). Disable showing Disable logging
---
It only happened once.
Does this convey any additional information?
-pu
next prev parent reply other threads:[~2023-05-21 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-20 15:47 [BUG] org-capture, level-2 heading, org-set-tags-command [9.6.6 ( @ /Users/pu/.emacs.d/elpa/org-9.6.6/)] Patrick Useldinger
2023-05-20 16:04 ` Ihor Radchenko
2023-05-20 18:41 ` Patrick Useldinger
2023-05-20 20:01 ` Ihor Radchenko
2023-05-20 21:06 ` Patrick Useldinger
2023-05-22 8:35 ` Ihor Radchenko
2023-05-21 9:00 ` Patrick Useldinger [this message]
2023-05-23 9:07 ` Patrick Useldinger
2023-05-23 9:15 ` Patrick Useldinger
2023-05-23 9:15 ` Patrick Useldinger
2023-05-24 8:56 ` Ihor Radchenko
2023-05-23 9:13 ` Patrick Useldinger
-- strict thread matches above, loose matches on Subject: below --
2023-05-19 21:23 Patrick Useldinger
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=99975c56-1ecc-b0f7-8b23-fdd3ee59bc27@gmail.com \
--to=uselpa@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).