From: Peter Davis <pfd@pfdstudio.com>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Exporting a subtree
Date: Wed, 18 Nov 2015 20:20:33 -0500 [thread overview]
Message-ID: <1447896033.2833795.443857521.11B0CE12@webmail.messagingengine.com> (raw)
In-Reply-To: <CA+M2ft9GZPwQLwZK3a2LTz9NQLCNe1oLy4UpqJmDuhrYrGPsBQ@mail.gmail.com>
On Wed, Nov 18, 2015, at 05:30 PM, John Hendy wrote:
> On Wed, Nov 18, 2015 at 2:43 PM, Peter Davis <pfd@pfdstudio.com> wrote:
> > John Hendy <jw.hendy@gmail.com> writes:
> >
> >> On Wed, Nov 18, 2015 at 2:29 PM, Peter Davis <pfd@pfdstudio.com> wrote:
> >>>
> >>> For the first time, I'm trying to export just a single subtree of my overall document, by typing
> >>>
> >>> C-c C-e C-s H O
> >>>
> >>> However, I get this error:
> >>>
> >>> apply: Wrong type argument: listp, #("Details, November 2015" 0 22 (:parent (#0)))
> >>>
> >>> The portion in quotes is the overall title of my document.
> >>>
> >>> Should this work? Is there something I need to do differently?
> >>
> >> Would you kindly provide a minimal working example? Perhaps create a
> >> dummy tree and indicate an analogous subtree export target so that the
> >> list can try to reproduce. Perhaps someone will catch from the error
> >> what the problem is, but having something to try is extremely helpful.
> >> Since my subtree export works, I'm at a loss for how to diagnose why
> >> yours doesn't.
> >
> >
> > Thanks, John. I think the problem lies with the #+title: option. If it's present, as in the short example below, then I get the
> > error. If not, it seems to work ok.
> >
> > +------------test.org------
> > #+title: Here's a document title
> >
> > * NOTE h1
> >
> > * TODO h1 also
> >
> > ** NOTE h2
> >
> > * Another subtree
> >
> > Here's some stuff I want to export to HTML.
> >
> > +------------------------
> >
>
> Is the attached what you'd expect? It works for me, and no issues with
> the title (which I don't think will apply since you're just exporting
> the subtree, but could be wrong).
>
>
> John
>
> > Thanks,
> > -pd
> >
> Email had 1 attachment:
> + 2015-11-18_162910.png
> 33k (image/png)
That looks right, but, as I said, it doesn't work for me if the #+title:
option is included.
Thanks,
--
Peter Davis
www.techcurmudgeon.com
www.timebums.com
next prev parent reply other threads:[~2015-11-19 1:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 20:43 Exporting a subtree Peter Davis
2015-11-18 22:30 ` John Hendy
2015-11-19 1:20 ` Peter Davis [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-19 13:51 Peter Davis
2015-11-19 14:39 ` Nick Dokos
2015-11-19 13:32 Peter Davis
2015-11-19 13:55 ` Nick Dokos
2015-11-18 20:29 Peter Davis
2015-11-18 20:35 ` John Hendy
2015-11-18 20:51 ` Nick Dokos
2015-11-20 16:21 ` Brett Viren
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=1447896033.2833795.443857521.11B0CE12@webmail.messagingengine.com \
--to=pfd@pfdstudio.com \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@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 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).