From: Rasmus <email@example.com>
Subject: Activate/deactivate export of inlinetasks with #+OPTIONS
Date: Tue, 14 Aug 2012 13:19:47 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
When writing documents, I think in terms of LaTeX. There, a common
option in `draft'. In orgmode inlinetasks is a draft-thingy to me. I
want to easily remove inlinetasks before exporting a final (that merely
means `pretty') version.
To reach an Org-ish solution I wrote the following trivial advice+extra,
which allows #+OPTIONS: inline:t or #+OPTIONS: inline:nil. It works
only with the new exporter (which is amazing!!!).
I'm hoping someone else could make use of it (although it is truly
trivial, but not being a programmer I appreciate finding `easy'
solutions on the internets).
'(:with-inlinetasks nil "inline" org-export-with-inlinetasks))
(defcustom org-export-with-inlinetasks t
"Non-nil means include INLINETASKS keywords in export.
When nil, remove all these keywords from the export."
(defadvice org-e-latex-inlinetask (after org-e-export-inlinetask-p)
"Return an inlinetask string if :with-inlinetasks is t otherwise
(if (not (plist-get info :with-inlinetasks))
(setq ad-return-value "")))
If this is of high enough standards it could perhaps be added to the
worg. . .
In theory, practice and theory are the same. In practice they are not
next reply other threads:[~2012-08-14 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 12:19 Rasmus [this message]
2012-08-14 12:49 ` Activate/deactivate export of inlinetasks with #+OPTIONS Rasmus
2012-08-14 19:17 ` Suvayu Ali
2012-08-14 21:48 ` Bastien
2012-08-16 10:51 ` Nicolas Goaziou
2012-08-16 11:05 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).