Re: [fr] allow overriding the likely unintended consequence of org-export-with-tasks

[Ihor Radchenko]

Samuel Wales <samologist@gmail.com> writes:

> 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."
> ...
> 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 see.

> 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.

Sometimes, there is point exporting nothing. In particular, for batch
exports. Also, nothing is too strong term. You will still have global
(empty) template being exported.

In other words, always exporting top-level heading is not always a good
idea.

> in case anybody wants the no-op, making it optional to export the top
> level heding would be copacetic.

One can modify

    ;; Ignore tasks, if specified by `:with-tasks' property.
        (and todo
             (or (not with-tasks)
                 (and (memq with-tasks '(todo done))
                      (not (eq todo-type with-tasks)))
                 (and (consp with-tasks) (not (member todo with-tasks)))))

condition in `org-export--skip-p' to take into account yet another
customization.

Patches welcome.

-- 
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>