From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcin Borkowski Subject: Re: Config best practices? Date: Sat, 21 Mar 2015 00:18:51 +0100 Message-ID: <87oannntpg.fsf@wmi.amu.edu.pl> References: <87r3sk1q56.fsf@wmi.amu.edu.pl> <86pp843uly.fsf@example.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50159) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YZ6C2-0001KS-5H for emacs-orgmode@gnu.org; Fri, 20 Mar 2015 19:19:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YZ6Bz-0004UG-09 for emacs-orgmode@gnu.org; Fri, 20 Mar 2015 19:19:06 -0400 Received: from msg.wmi.amu.edu.pl ([2001:808:114:2::50]:42718) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YZ6By-0004Sy-Ow for emacs-orgmode@gnu.org; Fri, 20 Mar 2015 19:19:02 -0400 Received: from localhost (localhost [127.0.0.1]) by msg.wmi.amu.edu.pl (Postfix) with ESMTP id 0F49C5AA70 for ; Sat, 21 Mar 2015 00:18:58 +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 tx22x-atfCTl for ; Sat, 21 Mar 2015 00:18:57 +0100 (CET) Received: from localhost (117-116.echostar.pl [213.156.117.116]) by msg.wmi.amu.edu.pl (Postfix) with ESMTPSA id 948115AA40 for ; Sat, 21 Mar 2015 00:18:57 +0100 (CET) In-reply-to: <86pp843uly.fsf@example.com> 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-20, at 10:07, Sebastien Vauban wrote= : > Hello Marcin, > > Marcin Borkowski wrote: >> I'm wondering what people do to keep the configuration of their Org >> files in order. > > I'm not sure to correctly grasp your objective. Could you restate it? Sure. Where do you put things like #+OPTIONS: toc:nil or #+SEQ_TODO: TODO | DONE or #+LATEX_HEADER: \newcommand{\eps}{\varepsilon} ? >> I use a dedicated top-level headline, with a COMMENT keyword, but >> I started to think that a :noexport: tag might be a better idea. >> >> Are there any advantages of one over the other, or other approaches >> altogether? > > I can tell you they aren't isomorphic... The noexport tag simply says > "don't export this subtree". The COMMENT keyword adds "don't run any > Babel code block in there". So I guess that =E2=80=93 since the lines with options etc. are not expor= ted anyway =E2=80=93 that using a :noexport: tag might be a better idea. Am = I right? >> The reason I'm asking is that I'm tweaking my org-one-to-many utility >> so that it propagates the config to all the generated files. > > Still not that clear to me. Maybe an ECM would clarify your request? As you wish. This is what I usually do. --8<---------------cut here---------------start------------->8--- * Headline * Another one ** Subheadline * COMMENT Config #+LATEX_HEADER: \newcommand{\eps}{\varepsilon} #+SEQ_TODO: TODO | DONE CANCEL #+OPTIONS: toc:nil --8<---------------cut here---------------end--------------->8--- > Best regards, > Seb Best, --=20 Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Faculty of Mathematics and Computer Science Adam Mickiewicz University