From: Nicolas Goaziou <email@example.com> To: Michael Dauer <firstname.lastname@example.org> Cc: email@example.com Subject: Re: BUG: export options properties drawer position and planning dates Date: Tue, 15 Jun 2021 08:07:35 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CAP7OBxKdaSUHRLLSwxkDqM2gHtocHh8BdYZWM7=EFTEctxEAzQ@mail.gmail.com> (Michael Dauer's message of "Mon, 14 Jun 2021 13:11:48 +0200") Hello, Michael Dauer <email@example.com> writes: > I would understand that the export would take the export settings of the > current heading to control the export of the complete subtree. That's correct. > 1. The much better logic would be that each node determines e.g. the > with-planning by its own (or inherited) properties. This is not how it is implemented. Export options are per export process, not per node. Besides, the above would not make sense for one-off items, like title:nil. I guess the much better logic would first need to distinguish global from local export options. But I don't think this is worth the trouble. > 2. This actually works when the scheduled date is (incorrectly) placed > below the drawer. It is not just treated as the first paragraph, but > omitted when the with-planning property of its node is nil, while normal > text would be exported. Would you mind providing an ECM for it? I'm not sure what example you're referring to. Regards, -- Nicolas Goaziou
next prev parent reply other threads:[~2021-06-15 6:08 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-08 13:17 Michael Dauer 2021-06-08 20:22 ` Nicolas Goaziou 2021-06-14 11:11 ` Michael Dauer 2021-06-15 6:07 ` Nicolas Goaziou [this message] 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: BUG: export options properties drawer position and planning dates' \ /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
Code repositories for project(s) associated with this 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).