From: Ihor Radchenko <yantar92@posteo.net>
To: Damien Cassou <damien@cassou.me>
Cc: emacs-orgmode@gnu.org
Subject: Re: Weird behavior of org-element-object-lex
Date: Thu, 20 Oct 2022 05:27:41 +0000 [thread overview]
Message-ID: <87v8of83oy.fsf@localhost> (raw)
In-Reply-To: <87fsfjd3ds.fsf@cassou.me>
Damien Cassou <damien@cassou.me> writes:
> here is the beginning of `org-element-object-lex`:
>
> (defun org-element--object-lex (restriction)
> "Return next object in current buffer or nil.
> RESTRICTION is a list of object types, as symbols, that should be
> looked after. This function assumes that the buffer is narrowed
> to an appropriate container (e.g., a paragraph)."
> (cond
> ((memq 'table-cell restriction) (org-element-table-cell-parser))
> ((memq 'citation-reference restriction)
> (org-element-citation-reference-parser))
> (t …)))
>
> From what I understand, if `restriction` includes 'table-cell (or
> 'citation-reference), and if the content isn't a table-cell,
> `org-element--object-lex` will immediately return nil without trying
> other object types.
>
> Is that a bug?
Not really. table-cell and citation-reference do not have a regexp
signature and are handled specially. For these two types of objects,
org-element--object-lex is called only when the parent is a table-row or
citation object. Not very elegant, but it is internal function, and it
works :)
--
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>
next prev parent reply other threads:[~2022-10-20 5:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 19:23 Weird behavior of org-element-object-lex Damien Cassou
2022-10-20 5:27 ` Ihor Radchenko [this message]
2022-10-20 6:00 ` Damien Cassou
2022-10-20 9:56 ` Ihor Radchenko
2022-10-20 13:41 ` Damien Cassou
2022-10-20 14:15 ` Damien Cassou
2022-10-20 16:50 ` Max Nikulin
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=87v8of83oy.fsf@localhost \
--to=yantar92@posteo.net \
--cc=damien@cassou.me \
--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).