From mboxrd@z Thu Jan 1 00:00:00 1970 From: Guido Van Hoecke Subject: Re: why is 'no' the default value of :tangle Date: Tue, 16 Apr 2013 15:09:05 +0200 Message-ID: References: <86wqs2vq7r.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:44094) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1US5dJ-0002D7-F3 for emacs-orgmode@gnu.org; Tue, 16 Apr 2013 09:09:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1US5dH-0006cN-61 for emacs-orgmode@gnu.org; Tue, 16 Apr 2013 09:09:13 -0400 Received: from mail-we0-x236.google.com ([2a00:1450:400c:c03::236]:47839) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1US5dG-0006cE-Uw for emacs-orgmode@gnu.org; Tue, 16 Apr 2013 09:09:11 -0400 Received: by mail-we0-f182.google.com with SMTP id m1so343834wea.41 for ; Tue, 16 Apr 2013 06:09:10 -0700 (PDT) In-Reply-To: <86wqs2vq7r.fsf@somewhere.org> (Sebastien Vauban's message of "Tue, 16 Apr 2013 10:23:36 +0200") 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: Sebastien Vauban Cc: emacs-orgmode@gnu.org "Sebastien Vauban" writes: > Christian Moe wrote: >> Guido Van Hoecke writes: >>> I am wondering why the default value of header argument :tangle is 'no' >>> rather than 'yes'. >> >> FWIW, the default makes sense to me. A document might contain lots of >> little code blocks for one purpose or another (testing, little >> utilities, version archive, etc.) that you don't want included in the >> tangled product. I see, that's a very valid point. >>> Back to google-calendar.org as an example. >>> >>> Is it normal that whomever wants to use the embedded elisp file needs >>> to edit the source and e.g. insert a '#+PROPERTY: tangle yes'? >>> >>> It is clear that this file will need to be tangled by every single >>> person that wants to use the embedded code, so should the default not >>> allow for tangling without having the edit the input file? >> >> Well, if you're distributing code for others to use in the form of >> source blocks in Org documents, it may be a courtesy to set `:tangle >> yes'. >> >> But that doesn't necessarily give users the tangled result where they >> want it on their system, with the filename they want, so they will often >> have to edit it anyway. > > And you can change the default for your Org installation, by changing the > default of the "tangle" header argument in your .emacs file: > > #+begin_src emacs-lisp > ;; add default arguments > (add-to-list 'org-babel-default-header-args > '(:tangle . "yes")) > #+end_src I should have known that this is configurable :) Thank you guys, Guido -- Regardless of whether a mission expands or contracts, administrative overhead continues to grow at a steady rate.