From: Jeffrey Spencer <jeffspencerd@gmail.com>
To: Detlef Steuer <detlef.steuer@gmx.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-Export Subtree Options Not Working
Date: Thu, 5 Jul 2012 01:35:49 +1000 [thread overview]
Message-ID: <CALmFPZ0ddBqA+z_XioWJgqSh58NW88dXEze02oeBDaF_KaJ=DQ@mail.gmail.com> (raw)
In-Reply-To: <20120704092142.080b2d61@vknecht-intel.unibw-hamburg.de>
[-- Attachment #1: Type: text/plain, Size: 3277 bytes --]
Sorry didn't finish the message.
That doesn't seem to work from what I have tried.
If for example it is
* 2012 :noexport:
** June :noexport:
*** Not going output
*** Want to export this and subtrees :export:
**** Also export
The above example won't export anything because the export is below the
:noexport:.
I just wrote a kbd macro to search up to the nearest tag in the structure I
define, select that subtree, and export. Then set to a key-binding to
reload each time but figured there was a better way to do this.
Or was interested for the reasons of creating a way to export a subtree at
a specific headline level always. Is there a way to go up from your current
level to a specific level in the subtree. Like if your on the 6th level but
want to go up to the third level heading. Is there a command or key
shortcut to do this essentially??
Cheers
On Wed, Jul 4, 2012 at 5:21 PM, Detlef Steuer <detlef.steuer@gmx.de> wrote:
> On Wed, 4 Jul 2012 14:03:24 +1000
> Jeffrey Spencer <jeffspencerd@gmail.com> wrote:
>
> > Thanks, that fixed it but another question.
> >
> > if you export the whole file then and not just the selection can you use
> a
> > tag or property to specify a different directory to export into instead
> of
> > the same directory as the org file. Will creating the Property Tag at the
> > top level work for this??
> >
> > Also, is there an easy way to tell it to ignore the first say 2 headers
> in
> > the file and only export starting with the third header. My first two
> > headers are just to keep track of dates eg.
> > * 2010
> > ** June
> >
> > I would rather these be ignored when doing the export. The only way I
> know
> > is to export the subtree.
>
> You should be able to use :noexport: on these.
>
> hth
> Detlef
>
>
> >
> > If there isn't then is there a way to write a command that would take the
> > current place your working in go up to the third level heading, select
> the
> > third level, and run an export command. Or the fastest way to do this via
> > key bindings?
> >
> > Cheers,
> > Jeff
> >
> > On Tue, Jul 3, 2012 at 7:29 PM, Nicolas Goaziou <n.goaziou@gmail.com>
> wrote:
> >
> > > Hello,
> > >
> > > Jeffrey Spencer <jeffspencerd@gmail.com> writes:
> > >
> > > > When I input subtree options for modifying the global options when
> > > > selecting with C-c @ and then exporting.
> > > >
> > > > The subtree options for example:
> > > >
> > > > #+EXPORT_OPTIONS: H:2 num:t toc:f \n:nil @:t ::t |:t ^:t -:t f:t *:t
> <:t
> > > > TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:nil
> > > > #+EXPORT_FILE_NAME: tester
> > > >
> > > > are not used and just ignored. Shouldn't these overide the file
> settings
> > > > from what I read in the org-manual. Where do these need to be
> placed. It
> > > is
> > > > right below the subtree I am selecting for export.
> > >
> > > You have to use headlines properties (with C-c C-x p) instead of
> > > keywords, i.e.
> > >
> > > --8<---------------cut here---------------start------------->8---
> > > * Headline
> > > :PROPERTIES:
> > > :EXPORT_TITLE: subtree-title
> > > :END:
> > > Paragraph
> > > --8<---------------cut here---------------end--------------->8---
> > >
> > >
> > > Regards,
> > >
> > > --
> > > Nicolas Goaziou
> > >
> >
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 5456 bytes --]
prev parent reply other threads:[~2012-07-04 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 8:13 Org-Export Subtree Options Not Working Jeffrey Spencer
2012-07-03 9:29 ` Nicolas Goaziou
2012-07-04 4:03 ` Jeffrey Spencer
2012-07-04 7:21 ` Detlef Steuer
2012-07-04 15:35 ` Jeffrey Spencer [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='CALmFPZ0ddBqA+z_XioWJgqSh58NW88dXEze02oeBDaF_KaJ=DQ@mail.gmail.com' \
--to=jeffspencerd@gmail.com \
--cc=detlef.steuer@gmx.de \
--cc=emacs-orgmode@gnu.org \
/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).