From: Ihor Radchenko <yantar92@posteo.net>
To: numbchild@gmail.com
Cc: Org mode <emacs-orgmode@gnu.org>
Subject: Re: [BUG] `org-element-at-point-no-context' error in flyspell `org-mode-flyspell-verify'
Date: Tue, 07 Nov 2023 09:00:41 +0000 [thread overview]
Message-ID: <87y1fa0wg6.fsf@localhost> (raw)
In-Reply-To: <6549d763.170a0220.d14a7.08b5@mx.google.com>
"Christopher M. Miles" <numbchild@gmail.com> writes:
> I got following error:
>
> #+begin_example
> Please report this to Org mode mailing list (M-x org-submit-bug-report).
> ⛔ Warning (org-element-cache): org-element--cache: Org parser error in Code.org::434180. Resetting.
> The error was: (wrong-number-of-arguments ((t) nil "Return outline-regexp with limited number of levels.
> The number of levels is controlled by `org-inlinetask-min-level'." (cond ((not (derived-mode-p 'org-mode)) outline-regexp) ((not (featurep 'org-inlinetask)) org-outline-regexp) (t (let* ((limit-level (1- org-inlinetask-min-level)) (nstars (if org-odd-levels-only (1- (* limit-level 2)) limit-level))) (format "\\*\\{1,%d\\} " nstars))))) 1)
This complains about too many arguments (1) in
`org-get-limited-outline-regexp'.
On main, `org-get-limited-outline-regexp' can accept an optional
argument, but it is not the case in the built-in Org mode.
I suspect some problem with mixed installation.
--
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>
prev parent reply other threads:[~2023-11-07 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 4:05 [BUG] `org-element-at-point-no-context' error in flyspell `org-mode-flyspell-verify' Christopher M. Miles
2023-11-07 9:00 ` 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=87y1fa0wg6.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=numbchild@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).