[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [fr] allow overriding the likely unintended consequence of org-expor
Re: [fr] allow overriding the likely unintended consequence of org-export-with-tasks
Thu, 23 Mar 2023 20:26:37 -0700
On 3/23/23, Ihor Radchenko <firstname.lastname@example.org> wrote:
> You can set org-export-with-tasks to '("REF"). It will make Org export
> REF todo keywords, but not other todo keywords.
this is true, but not relevant to my request. it won't as a practical
matter work around or solve the problem.
i wrote: "i would prefer the top level of the subtree to be exported
in all cases, because i have asked org to export. it does not matter
what kw it is set to or what the variable is set to."
of course, my request could be optional if desired, but agian it is
not useful to ask to export something and get a no-op.
as for ref [or blank] i do not want to have to keep or temporarily set
a todo kw, or lack of one, at the top level, merely to allow
exporting. this would be requiring me to maintain a keyword that i do
not want there in the outiine, OR a keyword that i do not want ther
ein the variable, both of which could have various consequences both
semantic and user-comprehension-oriented.
i find that having the feature apply also on the top level heading is
1] pointless, because there is no point in exporting nothing, and 2]
unexpected/surprising because you just SAID to export the subtree!,
and 3] unintended for similar reasons.
in case anybody wants the no-op, making it optional to export the top
level heding would be copacetic.
> 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>
The Kafka Pandemic
A blog about science, health, human rights, and misopathy: