From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Michael Dauer <mick.dauer@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: BUG: export options properties drawer position and planning dates
Date: Tue, 08 Jun 2021 22:22:16 +0200 [thread overview]
Message-ID: <87o8cghzt3.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAP7OBxKNAFqc2EG2zghgL3uaJvygmbFOFAe_C9KghZCNbLx7oQ@mail.gmail.com> (Michael Dauer's message of "Tue, 8 Jun 2021 15:17:31 +0200")
Hello,
Michael Dauer <mick.dauer@gmail.com> writes:
> There seems to be a bug in Org mode version 9.4.6 (9.4.6-gcf30f7:
> EXPORT_OPTIONS (at least p for with-planning) is only respected if there is
> no planning date placed above the properties drawer.
>
>>>>
> * TODO export options
> :PROPERTIES:
> :EXPORT_OPTIONS: p:nil
> :END:
> SCHEDULED: <2021-06-08 Di.>
> ** TODO l1
> :PROPERTIES:
> :EXPORT_OPTIONS: p:t
> :END:
> SCHEDULED: <2021-06-08 Di.>
> *** TODO l2
> SCHEDULED: <2021-06-08 Di.>
> **** TODO l3
> :PROPERTIES:
> :EXPORT_OPTIONS: p:nil
> :END:
> SCHEDULED: <2021-06-08 Di.>
> ***** TODO l4
> SCHEDULED: <2021-06-08 Di.>
> <<<
>
> produces the somehow expected behavior:
>>>>
> SCHEDULED: <2021-06-08>
>
>
> TODO l1
> =======
>
> SCHEDULED: <2021-06-08>
>
>
> TODO l2
> ~~~~~~~
>
> TODO l3
> -------
>
> SCHEDULED: <2021-06-08>
>
>
> * TODO l4
> <<<
>
> But it is syntactically incorrect since the planning dates have to be the
> first line below the heading.
This is correct, because the SCHEDULED lines are exported as paragraphs,
which is what they are.
> For the following syntactically correct
> snippet the export_options are ignored:
>>>>
> * TODO export options
> SCHEDULED: <2021-06-08 Di.>
> :PROPERTIES:
> :EXPORT_OPTIONS: p:nil
> :END:
> ** TODO l1
> SCHEDULED: <2021-06-08 Di.>
> :PROPERTIES:
> :EXPORT_OPTIONS: p:t
> :END:
> *** TODO l2
> SCHEDULED: <2021-06-08 Di.>
> **** TODO l3
> SCHEDULED: <2021-06-08 Di.>
> :PROPERTIES:
> :EXPORT_OPTIONS: p:nil
> :END:
> ***** TODO l4
> SCHEDULED: <2021-06-08 Di.>
> <<<
>>>>
> TODO l1
> =======
>
> TODO l2
> ~~~~~~~
>
> TODO l3
> -------
>
> * TODO l4
> <<<
>
> Same behavior I see with HTML export.
Did you use subtree export? Where was the point when you exported it?
For example, if I use a subtree export in the first section above, I get
no planning line, you if I subtree-export from the second section, i.e.,
"l1", all subsequent planning lines appear.
IOW, I cannot reproduce your issue.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2021-06-08 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 13:17 BUG: export options properties drawer position and planning dates Michael Dauer
2021-06-08 20:22 ` Nicolas Goaziou [this message]
2021-06-14 11:11 ` Michael Dauer
2021-06-15 6:07 ` Nicolas Goaziou
2021-06-15 12:01 ` Michael Dauer
2021-06-15 15:05 ` Nicolas Goaziou
2021-06-17 14:47 ` Michael Dauer
2021-06-17 17:21 ` Nicolas Goaziou
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=87o8cghzt3.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mick.dauer@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).