emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: why is 'no' the default value of :tangle
Date: Tue, 16 Apr 2013 10:23:36 +0200	[thread overview]
Message-ID: <86wqs2vq7r.fsf@somewhere.org> (raw)
In-Reply-To: m2eheaaoo8.fsf@christianmoe.com

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

Best regards,

Sebastien Vauban

  reply	other threads:[~2013-04-16  8:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16  7:18 why is 'no' the default value of :tangle Guido Van Hoecke
2013-04-16  8:02 ` Christian Moe
2013-04-16  8:23   ` Sebastien Vauban [this message]
2013-04-16 13:09     ` Guido Van Hoecke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86wqs2vq7r.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).