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

2023-03-24 Thread Ihor Radchenko
Samuel Wales 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 se

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

2023-03-24 Thread Samuel Wales
On 3/23/23, Ihor Radchenko 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 th

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

2023-03-23 Thread Ihor Radchenko
Samuel Wales writes: > when org-export-with-tasks is set to nil, tasks will not be exported, > but non-task entries will. > > you can make non-exported todo items and notes about your exported text. > > * REF this is the top level of the subtree > *** NOTE this is just a note and should not be ex

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

2023-03-03 Thread Samuel Wales
when org-export-with-tasks is set to nil, tasks will not be exported, but non-task entries will. you can make non-exported todo items and notes about your exported text. * REF this is the top level of the subtree *** NOTE this is just a note and should not be exported *** but this i want to expor