From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Config best practices? Date: Sat, 21 Mar 2015 09:01:46 -0400 Message-ID: <874mpezepx.fsf@pierrot.dokosmarshall.org> References: <87r3sk1q56.fsf@wmi.amu.edu.pl> <86pp843uly.fsf@example.com> <87oannntpg.fsf@wmi.amu.edu.pl> <87h9tfyrrg.fsf@pierrot.dokosmarshall.org> <87h9teognp.fsf@wmi.amu.edu.pl> <86a8z6y9ec.fsf@example.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47693) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YZJ2S-0000kE-Ri for emacs-orgmode@gnu.org; Sat, 21 Mar 2015 09:02:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YZJ2O-00005l-Ql for emacs-orgmode@gnu.org; Sat, 21 Mar 2015 09:02:04 -0400 Received: from plane.gmane.org ([80.91.229.3]:33340) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YZJ2O-00005a-Jc for emacs-orgmode@gnu.org; Sat, 21 Mar 2015 09:02:00 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YZJ2G-0007it-O3 for emacs-orgmode@gnu.org; Sat, 21 Mar 2015 14:01:52 +0100 Received: from pool-108-7-223-120.bstnma.fios.verizon.net ([108.7.223.120]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 21 Mar 2015 14:01:52 +0100 Received: from ndokos by pool-108-7-223-120.bstnma.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 21 Mar 2015 14:01:52 +0100 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 Sebastien Vauban writes: > Marcin Borkowski wrote: >> 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. > > As I wrote, you could choose for an ARCHIVE'd heading (one that's > always collapsed) or for a SETUPFILE? > The SETUPFILE sounds to me like the best solution, assuming that the different files are sharing configuration. -- Nick