From: Bernt Hansen <bernt@norang.ca>
To: Matt Lundin <mdl@imapmail.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Exporting narrowed subtrees to HTML
Date: Thu, 01 Jul 2010 03:07:52 -0400 [thread overview]
Message-ID: <87y6dv8yt3.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <87tyojnazx.fsf@fastmail.fm> (Matt Lundin's message of "Wed\, 30 Jun 2010 23\:20\:50 -0400")
Matt Lundin <mdl@imapmail.org> writes:
> Hi Bernt,
>
> Bernt Hansen <bernt@norang.ca> writes:
>>
>> I am working in a deeply nested org file and have narrowed to subtree
>> for the part of the file I'm working on which happens to start at
>> heading level 5.
>>
>> I want to export this narrowed subtree to HTML but the first HTML
>> heading level matches the file instead of starting from heading
>> level 2. This makes the resulting HTML output not as pretty as it could
>> be.
>
> If you select the subtree with C-c @ (outline-mark-subtree), it should
> export properly:
Cool! I didn't know about that. It only seems to work if transient
mark mode is enabled (but I have that on already).
I posted a patch for exporting a narrowed to subtree HTML export but it
gives slightly different results from selecting the tree with C-c @ --
the title (<h1>) is the name of the org-file similar to exporting the
entire document.
Thanks for pointing this out -- I'll probably start using C-c @ in the
future.
Regards,
Bernt
next prev parent reply other threads:[~2010-07-01 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 16:34 Exporting narrowed subtrees to HTML Bernt Hansen
2010-06-29 17:09 ` Rainer Stengele
2010-06-29 18:06 ` [PATCH] HTML export: Start the first exported headline at heading level 2 Bernt Hansen
2010-07-01 3:20 ` Exporting narrowed subtrees to HTML Matt Lundin
2010-07-01 7:07 ` Bernt Hansen [this message]
2010-07-01 7:26 ` Carsten Dominik
2010-07-01 7:29 ` Bernt Hansen
2010-07-01 8:12 ` Rainer Stengele
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=87y6dv8yt3.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.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).