From: Ihor Radchenko <yantar92@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Question about Org syntax
Date: Sun, 16 May 2021 16:01:07 +0800 [thread overview]
Message-ID: <87h7j3xg3g.fsf@localhost> (raw)
In-Reply-To: <877djz17cm.fsf@nicolasgoaziou.fr>
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> It should be a paragraph. I'll fix it soon.
>
> Note the problem can be reproduced with only
>
> * test
> :end:
Thanks!
Also, I have few more questions (or maybe bug reports) about
syntax/parsing:
1. Does org-element--current element suppose to return (paragraph ...)
on empty buffer?
2. Some of the element parsers honour LIMIT argument partially. Part of
the parsing is typically done using looking-at (ignoring the LIMIT)
and part is honouring it. This can backfire when LIMIT is before
first characteristic line of the element. For example take headline
parser:
<point>* Example<limit> headline
:contents-begin of the parsed headline will be _after_ :end
Or even
<point><limit>* example headline
:contents-begin is equal to :begin, sometimes leading to infinite
loops in org-element--parse-to called by org-element-cache (hence,
known bug with Emacs hangs when org-element-use-cache is non-nil)
Some of the parsers potentially causing similar issues are:
In particular, org-element-footnote-definition-parser,
org-element-headline-parser, org-element-inlinetask-parser,
org-element-plain-list-parser, org-element-property-drawer-parser,
org-element-babel-call-parser, org-element-clock-parser,
org-element-comment-parser, org-element-diary-sexp-parser,
org-element-fixed-width-parser, org-element-horizontal-rule-parser,
org-element-keyword-parser, org-element-node-property-parser,
org-element-paragraph-parser, ...
3. Some of the element parsers ignore LIMIT altogether:
org-element-item-parser, org-element-section-parser...
Is there any reason behind this? I though that parsing narrowed
buffer is supposed to honour narrowing. Also, ignoring LIMIT might
cause issue when trying to parse only visible elements.
Best,
Ihor
next prev parent reply other threads:[~2021-05-16 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 3:38 Question about Org syntax Ihor Radchenko
2021-05-16 7:11 ` Nicolas Goaziou
2021-05-16 8:01 ` Ihor Radchenko [this message]
2021-05-16 8:38 ` Nicolas Goaziou
2021-05-23 3:50 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7j3xg3g.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.