From: "Eddward DeVilla" <eddward@gmail.com>
To: Rainer Stengele <rainer.stengele@yahoo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: include file contents in org files?
Date: Tue, 21 Aug 2007 20:30:08 -0500 [thread overview]
Message-ID: <b71b18520708211830y1a7b4fd1r242de314220aec0@mail.gmail.com> (raw)
In-Reply-To: <fafmid$o21$1@sea.gmane.org>
On 8/21/07, Rainer Stengele <rainer.stengele@yahoo.de> wrote:
> Dear list,
>
> I'd like to have the initial lines (configuration) of any org file be
> the same. Yes, I could configure everything in my .emacs file - but I
> want to see my configuration - TAGS etc. - at the beginning of my org
> files.
> If I change anything in for example the TAGS section I have to do the
> change in each and every org files I use - which is stupid.
> Is there a possibility to include a file and show it maybe between a
> ruler set?
I've wanted something like that myself so that my org files /could/
stand on their own, but so I would need to edit them all if my
preferred defaults were to change. Ultimately, I've settled on having
an emacs config that I can move with my files. At some point I want
to use a package (I can't remember the name) that can split custom
configuration into multiple files.
What might be nice is to be able to put a token at the top of the file
to export the config from custom (or as much as reasonable) into the
file using a config name. So in custom you set a configuration name
(say eddwards-org-config) and at the top of your file you put
#+INLINE_CONFIG: eddwards-org-config
and org-mode would insert the configuration after it, replace any
config line that might already be there. If the keyword in the file
doesn't match what is in custom or if there isn't a name given in the
file or custom, then do not insert anything in the file. Org could
maybe update all of the agenda files as appropriate.
The reason for the name is so I can receive a file from someone else
(say my brother) and not have the config info in his file overlaid
with mine, distorting how he intended the file to be seen. That would
cover my needs for org, but I'll still probably get a custom splitter
since I'm starting to use emace for more things and I have at least
three separate machine I use it on and I'd like to share some of the
customizations.
Edd
prev parent reply other threads:[~2007-08-22 1:30 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
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 [this message]
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=b71b18520708211830y1a7b4fd1r242de314220aec0@mail.gmail.com \
--to=eddward@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rainer.stengele@yahoo.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).