From: Martin Leduc <mart_00@hotmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: org Publish subtree to pdf
Date: Sat, 17 Aug 2013 17:19:20 +0000 [thread overview]
Message-ID: <BLU168-W41CFB70CEE4B839A60A8B79A400@phx.gbl> (raw)
In-Reply-To: <87a9kg90x5.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
Thanks for your answers. That worked perfectly.
Martin
> From: n.goaziou@gmail.com
> To: mart_00@hotmail.com
> CC: emacs-orgmode@gnu.org
> Subject: Re: org Publish subtree to pdf
> Date: Sat, 17 Aug 2013 10:28:06 +0200
>
> Hello,
>
> Martin Leduc <mart_00@hotmail.com> writes:
>
> > I have a large org file with several projects in it. I can export one of
> > them (a subtree) to pdf by using C-c C-e C-s l o. However, I would like to
> > use the Publish function since it allows to export the pdf to another folder.
> >
> > However, by using C-s (Subtree option) and P (for publish) and x (to choose
> > template from org-publish-project-alist), the Subtree option does not seem
> > to work well.
>
> Subtree export is not meant to be used along with publishing. The latter
> works on complete files only.
>
> > The entire tree is exported though without the content of higher-level
> > headlines.
> >
> > Is it the normal behavior to be expected from the publish function ? What is
> > the best way to export in pdf to another location ?
>
> Use EXPORT_FILE_NAME node property. See penultimate paragraph from
> section 12.3 in the manual.
>
>
> Regards,
>
> --
> Nicolas Goaziou
[-- Attachment #2: Type: text/html, Size: 1696 bytes --]
prev parent reply other threads:[~2013-08-17 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-17 1:58 org Publish subtree to pdf Martin Leduc
2013-08-17 8:26 ` Suvayu Ali
2013-08-17 8:28 ` Nicolas Goaziou
2013-08-17 17:19 ` Martin Leduc [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BLU168-W41CFB70CEE4B839A60A8B79A400@phx.gbl \
--to=mart_00@hotmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.