From: Damien Cassou <damien@cassou.me>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Weird behavior of org-element-object-lex
Date: Thu, 20 Oct 2022 08:00:30 +0200 [thread overview]
Message-ID: <87czanc9vl.fsf@cassou.me> (raw)
In-Reply-To: <87v8of83oy.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> Damien Cassou <damien@cassou.me> writes:
>> 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 :)
I understand. Thank you. This is a problem for me but the workaround is
easy. For information, the rest of this email describes my problem and
the workaround but I'm not expecting anything from you, the workaround
is good enough.
I'm writing an exporter that is basically the same as ODT with some
differences that are mandatory to get articles published in the magazine
GNU/Linux Magazine. This magazine wants lists to have no special markups:
<text:p text:style-name="Normal">- item 1 ;</text:p>
<text:p text:style-name="Normal">- item 2 ;</text:p>
So, I wrote a plain-list transcoder and an item transcoder:
(defun ox-linuxmag--plain-list (plain-list contents _info)
contents)
(defun ox-linuxmag--item (item contents info)
(let* ((plain-content (buffer-substring-no-properties
(org-element-property :contents-begin item)
(org-element-property :contents-end item)))
(parse-tree (org-element-parse-secondary-string
plain-content
;; org-element-parse-secondary-string acts
;; weirdly if either 'table-cell or
;; 'citation-reference are included:
(cl-remove-if
(lambda (type) (seq-contains-p '(table-cell citation-reference) type))
org-element-all-objects)))
(item-content (org-export-data parse-tree info)))
(ox-linuxmag--format-text:p (format "- %s" item-content))))
The reason `ox-linuxmag--item` has to parse ITEM again is because
CONTENTS contains "<text:p text:style-name="Normal">item 1 ;</text:p>"
which misses the initial dash "-" character: i.e., I would like "- item
1 ;" in the paragraph instead.
As you can see, the code uses `org-element-parse-secondary-string` with
most of `org-element-all-objects` as RESTRICTION argument but neither
`table-cell` nor `citation-reference`.
Do you see a simpler way to achieve this?
--
Damien Cassou
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
next prev parent reply other threads:[~2022-10-20 6:11 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
2022-10-20 6:00 ` Damien Cassou [this message]
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=87czanc9vl.fsf@cassou.me \
--to=damien@cassou.me \
--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).