From: Carsten Dominik <dominik@science.uva.nl>
To: Rainer Stengele <rainer.stengele@diplan.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: include file contents in org files?
Date: Wed, 22 Aug 2007 11:42:26 +0200 [thread overview]
Message-ID: <cbdf2f39923e139d9eeb0e87fa598c6f@science.uva.nl> (raw)
In-Reply-To: <fagvql$2o0$1@sea.gmane.org>
On Aug 22, 2007, at 11:32, Rainer Stengele wrote:
> Adam Spiers schrieb:
>> Bastien (bzg@altern.org) wrote:
>>> Rainer Stengele <rainer.stengele@yahoo.de> writes:
>>>
>>>> I'd like to have the initial lines (configuration) of any org file
>>>> be
>>>> the same.
>>> Perhaps we can use Tempo [1] or Templates [2] for this?
>> If I understand Rainer's original requirements, that wouldn't work,
>> because once expansion had been performed across multiple files, you
>> would still need to edit them all if you needed to make a change to
>> the common component. An include mechanism sounds like a nice idea to
>> me.
>
> Adam, you've got it right.
> I would like to have something like a #include under C but also see
> the contents of the included file.
> The include "update" could take place whenever the org file is opened
> or maybe by request "org-update-includes" or whatever.
While I maybe can see the use of having an #include mechanism,
I don't see why you'd want to *see* the included stuff.
It is just as easy to look at the include file itself, and if it is
the same for every file you use, you'd have it memorized soon enough.
- Carsten
next prev parent reply other threads:[~2007-08-22 9:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 21:47 include file contents in org files? Rainer Stengele
2007-08-21 23:44 ` Bastien
2007-08-22 9:10 ` Adam Spiers
2007-08-22 9:32 ` Rainer Stengele
2007-08-22 9:42 ` Carsten Dominik [this message]
2007-08-22 10:44 ` Rainer Stengele
2007-08-22 10:54 ` Rainer Stengele
2007-08-22 11:07 ` Carsten Dominik
2007-08-22 20:25 ` Rainer Stengele
2007-08-23 17:55 ` Carsten Dominik
2007-08-23 23:32 ` Daniel J. Sinder
2007-08-24 2:57 ` Carsten Dominik
2007-08-24 11:30 ` Rainer Stengele
2007-08-22 1:30 ` Eddward DeVilla
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=cbdf2f39923e139d9eeb0e87fa598c6f@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=rainer.stengele@diplan.de \
/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).