From: Nick Dokos <email@example.com>
To: John Tarbotton <firstname.lastname@example.org>
Cc: email@example.com, firstname.lastname@example.org
Subject: Re: Hiding Properties and Log drawers from export.
Date: Mon, 14 Mar 2011 12:51:47 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: Message from John Tarbotton <firstname.lastname@example.org> of "Mon, 14 Mar 2011 15:51:38 -0000." <loom.20110314T164200email@example.com>
John Tarbotton <firstname.lastname@example.org> wrote:
> Nick Dokos <nicholas.dokos <at> hp.com> writes:
> > John Tarbotton <jtarbotton <at> gmail.com> wrote:
> > > Is there a way to prevent the Property and Logfile Drawers from
> > > being exported?
> > Check the value of the following variable (with C-h v
> > org-export-with-drawers <RET>):
> > Nick
> Thanks for the reply that would seem to be what I need. In fact it got me
> half way there. I set it nil using the menu. The LOGFILE drawers are gone
> but the property drawers are still there. The documentation indicates it
> works with the PROPERTIES draw so I'll keep trying. Maybe I did something
> to the .org file that is messing it up.
That's strange. Maybe you can try by setting the variable in the file explicitly.
By uncommenting one of the OPTIONS lines below and leaving the other two commented
out, I can get just the LOGBOOK exported; or both LOGBOOK and PROPERTIES; or neither.
:COLUMNS: %40ITEM %Link1 %Link2
** Test Heading
CLOCK: [2011-03-14 Mon 12:35]--[2011-03-14 Mon 12:35] => 0:00
:Link1: [[* Target]]
** Test File
next prev parent reply other threads:[~2011-03-14 16:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 13:12 Hiding Properties and Log drawers from export John Tarbotton
2011-03-14 14:37 ` Nick Dokos
2011-03-14 15:51 ` John Tarbotton
2011-03-14 16:46 ` John Tarbotton
2011-03-14 17:00 ` Nick Dokos
2011-03-14 16:51 ` Nick Dokos [this message]
2011-03-14 14:46 ` Nick Dokos
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).