From mboxrd@z Thu Jan 1 00:00:00 1970 From: Darlan Cavalcante Moreira Subject: Re: How to uniformly configure multiple org files Date: Fri, 05 Aug 2011 15:47:09 -0300 Message-ID: <4e3c3ac9.418fec0a.383a.5f36@mx.google.com> References: <4e3c2e5a.08b5ec0a.3587.5838@mx.google.com> <20110805180917.GA6630@soloJazz.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from eggs.gnu.org ([140.186.70.92]:53185) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QpPQr-0003QX-4b for emacs-orgmode@gnu.org; Fri, 05 Aug 2011 14:47:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QpPQp-0003qS-Sq for emacs-orgmode@gnu.org; Fri, 05 Aug 2011 14:47:41 -0400 Received: from mail-gx0-f169.google.com ([209.85.161.169]:42171) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QpPQp-0003qN-Nk for emacs-orgmode@gnu.org; Fri, 05 Aug 2011 14:47:39 -0400 Received: by gxk23 with SMTP id 23so523551gxk.0 for ; Fri, 05 Aug 2011 11:47:39 -0700 (PDT) In-Reply-To: <20110805180917.GA6630@soloJazz.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org 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 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). > >