From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastien Vauban Subject: Re: Config best practices? Date: Sat, 21 Mar 2015 10:42:03 +0100 Message-ID: <86a8z6y9ec.fsf@example.com> 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> Mime-Version: 1.0 Content-Type: text/plain Return-path: 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org 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? Best regards, Seb -- Sebastien Vauban