* How to uniformly configure multiple org files
@ 2011-08-05 17:54 Darlan Cavalcante Moreira
2011-08-05 18:09 ` Juan Pechiar
0 siblings, 1 reply; 3+ messages in thread
From: Darlan Cavalcante Moreira @ 2011-08-05 17:54 UTC (permalink / raw)
To: Orgmode Mailing List
In each org file I usually put several configuration lines such
as #+STARTUP, #+OPTIONS, #+LINK, etc. Is there a way to keep these
configurations in a single file and then "include" this file in each org
file I want? This would be particularly useful for projects.
What I have in mind is something like a #+INCLUDE_CONF keyword similar
to #+INCLUDE, but while #+INCLUDE includes the content of one org-file into
another, the #+INCLUDE_CONF would include the configuration comments while
ignoring the content (so that we could use headings to separate the
configuration comments, for instance).
--
Darlan
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: How to uniformly configure multiple org files
2011-08-05 17:54 How to uniformly configure multiple org files Darlan Cavalcante Moreira
@ 2011-08-05 18:09 ` Juan Pechiar
2011-08-05 18:47 ` Darlan Cavalcante Moreira
0 siblings, 1 reply; 3+ messages in thread
From: Juan Pechiar @ 2011-08-05 18:09 UTC (permalink / raw)
To: Darlan Cavalcante Moreira; +Cc: Orgmode Mailing List
Hi Darlan,
Please check #SETUPFILE
http://orgmode.org/manual/In_002dbuffer-settings.html
Regards,
.j.
On Fri, Aug 05, 2011 at 02:54:30PM -0300, Darlan Cavalcante Moreira wrote:
>
> In each org file I usually put several configuration lines such
> as #+STARTUP, #+OPTIONS, #+LINK, etc. Is there a way to keep these
> configurations in a single file and then "include" this file in each org
> file I want? This would be particularly useful for projects.
>
> What I have in mind is something like a #+INCLUDE_CONF keyword similar
> to #+INCLUDE, but while #+INCLUDE includes the content of one org-file into
> another, the #+INCLUDE_CONF would include the configuration comments while
> ignoring the content (so that we could use headings to separate the
> configuration comments, for instance).
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: How to uniformly configure multiple org files
2011-08-05 18:09 ` Juan Pechiar
@ 2011-08-05 18:47 ` Darlan Cavalcante Moreira
0 siblings, 0 replies; 3+ messages in thread
From: Darlan Cavalcante Moreira @ 2011-08-05 18:47 UTC (permalink / raw)
To: Juan Pechiar; +Cc: Orgmode Mailing List
Thanks, this is exactly what I need.
At Fri, 5 Aug 2011 15:09:17 -0300,
Juan Pechiar <juan@pechiar.com> wrote:
>
> Hi Darlan,
>
> Please check #SETUPFILE
>
> http://orgmode.org/manual/In_002dbuffer-settings.html
>
> Regards,
> .j.
>
> On Fri, Aug 05, 2011 at 02:54:30PM -0300, Darlan Cavalcante Moreira wrote:
> >
> > In each org file I usually put several configuration lines such
> > as #+STARTUP, #+OPTIONS, #+LINK, etc. Is there a way to keep these
> > configurations in a single file and then "include" this file in each org
> > file I want? This would be particularly useful for projects.
> >
> > What I have in mind is something like a #+INCLUDE_CONF keyword similar
> > to #+INCLUDE, but while #+INCLUDE includes the content of one org-file into
> > another, the #+INCLUDE_CONF would include the configuration comments while
> > ignoring the content (so that we could use headings to separate the
> > configuration comments, for instance).
> >
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-08-05 18:47 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-08-05 17:54 How to uniformly configure multiple org files Darlan Cavalcante Moreira
2011-08-05 18:09 ` Juan Pechiar
2011-08-05 18:47 ` Darlan Cavalcante Moreira
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).