emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <c.dominik@uva.nl>
To: Peter Jones <mlists@pmade.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Additional Properties for Export
Date: Tue, 20 May 2008 19:22:11 +0200	[thread overview]
Message-ID: <FC2D9BF5-0570-4980-8CCE-36AA877423EC@uva.nl> (raw)
In-Reply-To: <m23aoex72d.fsf@pmade.com>

Hi Peter, how do you export a single subtree?  If you do it by  
selecting the subtree as the region, then the headling of the subtree  
will become the title for export. - - - Actually, I just tried, and  
that does not work.  Bug is fixed now, in the git-repo.

However, an EXPORT_TITLE property is a good idea, and I have added  
that, too.

The EXPORT_OPTIONS property is a lot harder, can you motivate why and  
how you would want it?

- Carsten

On May 20, 2008, at 12:28 AM, Peter Jones wrote:
> As you can tell from my recent questions, I've been doing a lot of
> exporting from Org lately.  Here are a few things I'd like some
> feedback on.
>
> I would like to be able to set a TITLE property for a sub-tree, and
> when I export just that sub-tree, the document title will be taken
> from that property instead of the file global #+TITLE:.
>
> Right now, when I export a sub-tree, I need to manually change the
> #+TITLE: line so that the exported document will have an appropriate
> title.
>
> It would also be nice to have an OPTIONS property (or maybe
> EXPORT_OPTIONS) where I could override the #+OPTIONS line for each
> sub-tree.
>
> Does this seem generally useful?
>
> Here is an example document:
>
> #+TITLE: Client Work
>
> * Client A
> ** Project Foo Requirements
>   :PROPERTIES:
>   :ID:       a-foo
>   :TITLE:    Foo Application Requirements
>   :COLUMNS:  %50ITEM(Task) %5Effort(Effort Estimate){:} %5TODO(State)
>   :END:
> *** DONE Feature 1
> *** TODO Feature 2
> ** Project Bar Requirements
>   :PROPERTIES:
>   :ID:       a-bar
>   :TITLE:    Bar Application Requirements
>   :COLUMNS:  %50ITEM(Task) %5Effort(Effort Estimate){:}
>   :END:
> *** TODO Feature 1
> *** TODO Feature 2
>
> -- 
> Peter Jones, pmade inc.
> http://pmade.com
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2008-05-20 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19 22:28 Additional Properties for Export Peter Jones
2008-05-20 17:22 ` Carsten Dominik [this message]
2008-05-20 19:41   ` Peter Jones
2008-05-20 21:10     ` Carsten Dominik
2008-05-21  7:50     ` Carsten Dominik

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=FC2D9BF5-0570-4980-8CCE-36AA877423EC@uva.nl \
    --to=c.dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=mlists@pmade.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).