From: Nicolas Goaziou <n.goaziou@gmail.com>
To: "William LÉCHELLE" <william.lechelle@ens-lyon.fr>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Subtasks cookies out of export
Date: Mon, 27 Aug 2012 11:41:56 +0200 [thread overview]
Message-ID: <871uisacyj.fsf@gmail.com> (raw)
In-Reply-To: <87ehmsdb8q.wl%william.lechelle@ens-lyon.fr> ("William \=\?utf-8\?Q\?L\=C3\=89CHELLE\=22's\?\= message of "Mon, 27 Aug 2012 03:50:45 -0400")
Hello,
William LÉCHELLE <william.lechelle@ens-lyon.fr> writes:
> I use subtasks cookies in titles, as described in
> http://orgmode.org/manual/Breaking-down-tasks.html, along with todo keywords,
> when writing a document to be exported, and I'd like then NOT to be exported
> (for they're org metadata). Exporting to pdf, still using the default
> exporter. I would have guess there would be an #+option for that (removing the
> progress cookies), but I didn't find it in the export options page.
>
> How much is that possible ?
In the default exporter, you can add a function to
`org-export-preprocess-hook' which will carefully remove every
statistics cookie en the buffer.
In the next exporter, you can still use that hook (named
`org-export-before-parsing-hook' this time) or use the following:
#+BEGIN_SRC emacs-lisp
(defun my-ignore-stat-cookies (cookie backend info)
"Ignore every statistics cookie in every export back-end."
"")
(add-to-list 'org-export-filter-statistics-cookie-functions
'my-ignore-stat-cookies)
#+END_SRC
So, it will quite simple already to ignore them. Do you (and other
users) think it's worth to add a customizable variable and an entry in
the #+OPTIONS: line (perhaps with a "stat:nil" value) to achieve the
same?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-08-27 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 7:50 Subtasks cookies out of export William LÉCHELLE
2012-08-27 9:41 ` Nicolas Goaziou [this message]
2012-08-27 10:07 ` William Léchelle
2012-08-27 13:42 ` Nicolas Goaziou
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=871uisacyj.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=william.lechelle@ens-lyon.fr \
/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).