From: Mark Elston <firstname.lastname@example.org>
Subject: Re: include an .org file and lower the level of all its headers
Date: Wed, 10 Nov 2010 11:06:23 -0800 [thread overview]
Message-ID: <4CDAED2F.email@example.com> (raw)
I don't know about Jianshi's specific needs but I have also wanted
the same thing for myself.
I often put together "standard" information on a variety of topics that
I talk about in separate files. When I put together a talk for a given
topic I include many of these sub-topics in a given talk. However, I
usually need different "surrounding" material to preface these topics
and draw conclusions relevant to the main topic. I would like to be
able to continue to have these sub-topics in separate files and just
include them (by reference - so to speak) in my notes without having
to adjust their heading levels or pasting them directly into my notes.
On 11/10/2010 3:09 AM, Scot Becker wrote:
> I've never heard of any way to do that with an #+INCLUDE. There are
> variables that automatically demote subtrees that you yank in with
> CTRL-Y, but that's a hard-INCLUDE, so to speak, and you probably have
> your reasons for wanting to keep them in separate files.
> On Wed, Nov 10, 2010 at 9:46 AM, Jianshi Huang <firstname.lastname@example.org
> <mailto:email@example.com>> wrote:
> I know I can include any file using #+INCLUDE.
> I need to include several org files, but they were edited
> independently as a complete document.
> Now I want to lower the levels of headers in these org files
> automatically during inclusion. Is there a way to do that?
next prev parent reply other threads:[~2010-11-10 19:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 9:46 include an .org file and lower the level of all its headers Jianshi Huang
2010-11-10 11:09 ` Scot Becker
2010-11-10 19:06 ` Mark Elston [this message]
2010-11-10 19:35 ` Samuel Wales
2010-11-12 19:42 ` Carsten Dominik
2010-11-14 7:01 ` Puneeth
2010-11-15 10:18 ` Carsten Dominik
2011-04-20 18:48 ` Robert Goldman
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).