From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcin Borkowski Subject: Re: Config best practices? Date: Sat, 21 Mar 2015 10:15:22 +0100 Message-ID: <87h9teognp.fsf@wmi.amu.edu.pl> References: <87r3sk1q56.fsf@wmi.amu.edu.pl> <86pp843uly.fsf@example.com> <87oannntpg.fsf@wmi.amu.edu.pl> <87h9tfyrrg.fsf@pierrot.dokosmarshall.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40757) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YZFVI-0003xw-Lj for emacs-orgmode@gnu.org; Sat, 21 Mar 2015 05:15:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YZFVC-0007ok-UN for emacs-orgmode@gnu.org; Sat, 21 Mar 2015 05:15:36 -0400 Received: from msg.wmi.amu.edu.pl ([2001:808:114:2::50]:54839) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YZFVC-0007oS-NV for emacs-orgmode@gnu.org; Sat, 21 Mar 2015 05:15:30 -0400 Received: from localhost (localhost [127.0.0.1]) by msg.wmi.amu.edu.pl (Postfix) with ESMTP id 3F5375AE84 for ; Sat, 21 Mar 2015 10:15:29 +0100 (CET) Received: from msg.wmi.amu.edu.pl ([127.0.0.1]) by localhost (msg.wmi.amu.edu.pl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p7AFUQTVNIXr for ; Sat, 21 Mar 2015 10:15:29 +0100 (CET) Received: from localhost (117-116.echostar.pl [213.156.117.116]) by msg.wmi.amu.edu.pl (Postfix) with ESMTPSA id F31725AE83 for ; Sat, 21 Mar 2015 10:15:28 +0100 (CET) In-reply-to: <87h9tfyrrg.fsf@pierrot.dokosmarshall.org> 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: emacs-orgmode@gnu.org On 2015-03-21, at 04:05, Nick Dokos wrote: > Yes, but why do you do that? What are you trying to accomplish? What > does "keeping the configuration in order" mean? I have that org-one-to-many utility, which splits the Org file at (selected) headings, effectively making them separate Org files. If I e.g. use LaTeX macro definitions, or custom (per-file) TODO keywords in that file, it makes sense to put the same configs in the files split from the main one. Putting them into their own headline may be the simplest way to tell org-one-to-many what to copy to each generated file. I don't like putting them at the top; while #+TITLE or #+AUTHOR do make sense there (and don't in the split files!), cluttering the first few screens with e.g. LaTeX definitions is not my favorite way of using Org-mode. Best, -- Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University