From: Richard Lawrence <email@example.com>
To: Matt Price <firstname.lastname@example.org>, Org Mode <email@example.com>
Subject: Re: allow HTML block to escape from outline-text div? WAS: BUG? unable to surround subtrees with html tag
Date: Tue, 22 Jun 2021 10:30:00 +0200 [thread overview]
Message-ID: <875yy6ti7r.fsf@aquinas> (raw)
Matt Price <firstname.lastname@example.org> writes:
>> I would like to be able to surround some portion of a subtree with a tag,
>> * parent
>> some text
>> #+HTML: <div class="box">
>> ** child 2
>> some boxed content
>> ** child 2
>> more boxed content
>> ** child 3
>> unboxed content
> I don't know if there is a way to somehow slide my own html in between the
> outine-text element and the outline-container element for a child subtree.
> If someone knows a way to do this, I'd appreciate a pointer, but for now I
> think I have to find another way to accomplish this.
Is it important that your two headlines in the boxed content export as <h2>?
If not, you could just use a structure like
*** Boxed Child 1
*** Boxed Child 2
** Unboxed Child
and use something like the ignoreheading filter (see Worg's "Org Hacks"
page) to prevent "Box" from producing a separate header, and maybe
various properties (e.g. UNNUMBERED?) to keep the boxed children from
appearing as part of the main outline.
Otherwise, #+INCLUDE comes to mind as a possible solution.
Would one of those options work for you?
next prev parent reply other threads:[~2021-06-22 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 19:07 BUG? unable to surround subtrees with html tag Matt Price
2021-06-21 22:01 ` allow HTML block to escape from outline-text div? WAS: " Matt Price
2021-06-22 8:30 ` Richard Lawrence [this message]
2021-06-22 16:31 ` Matt Price
2021-07-01 16:18 ` Timothy
2021-07-06 3:58 ` Matt Price
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).