emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Patrick Drechsler <patrick@pdrechsler.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: limiting export by category, tag or property
Date: Mon, 16 Jul 2007 08:50:20 +0200	[thread overview]
Message-ID: <cefa3f077be6225cc845a782b0f47823@science.uva.nl> (raw)
In-Reply-To: <87ps2tnnma.fsf@pdrechsler.de>


On Jul 16, 2007, at 3:28, Patrick Drechsler wrote:

> Hi,
>
> what is a good way of excluding certain sections of a file from being
> exported (similar to `C-c C-e v').
>
> Can this be done by setting "category", "tag" or "property"?

The tag ARCHIVED will keep a subtree from exporting (depending on the
variable `org-export-with-archived-trees').  But I guess this
is not what you want.

A section starting with the word `org-comment-string' will not
be exported.  Maybe, if you don't use this for comments, change
it to "PRIVATE" or whatever.  Then you can do

   * info for all
     Lets all hail the boss
   * info for group
     Make sure that you ask me before you ask the boss,
     because he is so busy with important stuff.
   * PRIVATE info
     Actually, the boss is a total crackpot.


Properties are new.  I guess if I had known about properties
2 years ago, #+CATEGORY would have become a property.
There are a number of things that could potentially
be set through properties.  This needs more time,
because I am wary about having too many different ways to
set the same variable.  But things that are candidates are:

- Category
- Archive location
- File name for export of a subtree


Carsten

      reply	other threads:[~2007-07-16  6:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16  1:28 limiting export by category, tag or property Patrick Drechsler
2007-07-16  6:50 ` Carsten Dominik [this message]

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=cefa3f077be6225cc845a782b0f47823@science.uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=patrick@pdrechsler.de \
    /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).