From: Ihor Radchenko <yantar92@posteo.net>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [fr] allow overriding the likely unintended consequence of org-export-with-tasks
Date: Thu, 23 Mar 2023 14:59:35 +0000 [thread overview]
Message-ID: <87sfdvldig.fsf@localhost> (raw)
In-Reply-To: <CAJcAo8sgt6UEtpkYcDMftOu71-2yoMQWkiQn5XqtD5xxE4xNsA@mail.gmail.com>
Samuel Wales <samologist@gmail.com> 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 exported
> *** but this i want to export of course
>
> you can specify other values for the variable that have a similar
> effect. let's use nil for this example.
>
> this is highly useful, but in my case, there is an unintended
> consequence. the REF todo kw prevents anything from being exported,
> for subtree or region export. not exporting is not a useful behavior.
> 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.
You can set org-export-with-tasks to '("REF"). It will make Org export
REF todo keywords, but not other todo keywords.
--
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>
next prev parent reply other threads:[~2023-03-23 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 7:03 [fr] allow overriding the likely unintended consequence of org-export-with-tasks Samuel Wales
2023-03-23 14:59 ` Ihor Radchenko [this message]
2023-03-24 3:26 ` Samuel Wales
2023-03-24 12:00 ` Ihor Radchenko
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=87sfdvldig.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@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).