From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christian Moe <mail@christianmoe.com>
Subject: Re: why is 'no' the default value of :tangle
Date: Tue, 16 Apr 2013 10:02:31 +0200
Message-ID: <m2eheaaoo8.fsf@christianmoe.com>
References: <m2li8jueod.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:48336)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@christianmoe.com>) id 1US0o8-0008Pp-Ap
	for emacs-orgmode@gnu.org; Tue, 16 Apr 2013 04:00:10 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@christianmoe.com>) id 1US0o6-0003Di-PQ
	for emacs-orgmode@gnu.org; Tue, 16 Apr 2013 04:00:04 -0400
Received: from mail2.b1.hitrost.net ([91.185.211.205]:40306)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@christianmoe.com>) id 1US0o6-00037A-Jd
	for emacs-orgmode@gnu.org; Tue, 16 Apr 2013 04:00:02 -0400
In-reply-to: <m2li8jueod.fsf@gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: Guido Van Hoecke <guivho@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>


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.

> 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.

Yours,
Christian