From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Spiers Subject: Re: include file contents in org files? Date: Wed, 22 Aug 2007 10:10:42 +0100 Message-ID: <20070822091042.GC25403@atlantic.linksys.moosehall> References: <87bqd0qwql.fsf@bzg.ath.cx> Reply-To: Adam Spiers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1INmEi-00085c-UR for emacs-orgmode@gnu.org; Wed, 22 Aug 2007 05:10:49 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1INmEh-00085Q-3H for emacs-orgmode@gnu.org; Wed, 22 Aug 2007 05:10:47 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1INmEg-00085N-SC for emacs-orgmode@gnu.org; Wed, 22 Aug 2007 05:10:46 -0400 Received: from mail.beimborn.com ([70.84.38.100]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1INmEg-00083Q-Hb for emacs-orgmode@gnu.org; Wed, 22 Aug 2007 05:10:46 -0400 Received: from mail.beimborn.com (localhost.localdomain [127.0.0.1]) by mail.beimborn.com (8.12.11.20060308/8.12.8) with ESMTP id l7M9AimW013696 for ; Wed, 22 Aug 2007 04:10:44 -0500 Received: from localhost (localhost [[UNIX: localhost]]) by mail.beimborn.com (8.12.11.20060308/8.12.11/Submit) id l7M9Aiaj013691 for emacs-orgmode@gnu.org; Wed, 22 Aug 2007 10:10:44 +0100 Content-Disposition: inline In-Reply-To: <87bqd0qwql.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Bastien (bzg@altern.org) wrote: > Rainer Stengele 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.