From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rainer Stengele Subject: Re: include file contents in org files? Date: Wed, 22 Aug 2007 12:44:45 +0200 Message-ID: References: <87bqd0qwql.fsf@bzg.ath.cx> <20070822091042.GC25403@atlantic.linksys.moosehall> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1INnho-00020C-Jy for emacs-orgmode@gnu.org; Wed, 22 Aug 2007 06:44:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1INnhn-000200-9Q for emacs-orgmode@gnu.org; Wed, 22 Aug 2007 06:44:55 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1INnhn-0001zx-4G for emacs-orgmode@gnu.org; Wed, 22 Aug 2007 06:44:55 -0400 Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1INnhm-0000hx-Jo for emacs-orgmode@gnu.org; Wed, 22 Aug 2007 06:44:54 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1INnhg-0005WV-5H for emacs-orgmode@gnu.org; Wed, 22 Aug 2007 12:44:48 +0200 Received: from p57af19dd.dip0.t-ipconnect.de ([87.175.25.221]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Aug 2007 12:44:48 +0200 Received: from rainer.stengele by p57af19dd.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Aug 2007 12:44:48 +0200 In-Reply-To: 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 Carsten Dominik schrieb: > ... > > 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 Well - thinking hard about it I have to agree it's not really necessary to see the contents of the file. Seeing it at the beginning of any org file was just quite convenient when I started using org-mode and was still modifying my used TAG set etc. Agreed, a simple "standard" include mechanism would do it very well! Rainer