From: Michael Dauer <mick.dauer@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-element API does not identify inlinetasks (correctly)
Date: Thu, 29 Sep 2022 13:36:27 +0200 [thread overview]
Message-ID: <CAP7OBx+B-QuEcfa5noCZU5-ijWUQTbBcAwSB=FAs1YBPCfsTaw@mail.gmail.com> (raw)
In-Reply-To: <87v8p65sy9.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
There is a (require 'org-inlinetask), and I use inlinetasks a lot.
Am Do., 29. Sept. 2022 um 13:18 Uhr schrieb Ihor Radchenko <
yantar92@gmail.com>:
> Michael Dauer <mick.dauer@gmail.com> writes:
>
> > Inlinetasks are always interpreted to be of type heading. This causes
> > multiple issues e.g with export.
> >
> > I think that I could track it to the function
> org-element--current-element,
> > where the check for headings is before the one for inlinetasks, while
> > inlinetask is just a sub-type of heading.
>
> Inlinetasks are not parsed by Org by default. You must first load
> org-inlinetask module to enable the parsing.
>
> Without org-inlinetask being loaded, inlinetasks are treated as ordinary
> headings.
>
> --
> Ihor Radchenko,
> 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
>
[-- Attachment #2: Type: text/html, Size: 1596 bytes --]
next prev parent reply other threads:[~2022-09-29 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 11:04 org-element API does not identify inlinetasks (correctly) Michael Dauer
2022-09-29 11:19 ` Ihor Radchenko
2022-09-29 11:36 ` Michael Dauer [this message]
2022-09-29 11:40 ` 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
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='CAP7OBx+B-QuEcfa5noCZU5-ijWUQTbBcAwSB=FAs1YBPCfsTaw@mail.gmail.com' \
--to=mick.dauer@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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).