emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Guido Van Hoecke <guivho@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: why is 'no' the default value of :tangle
Date: Tue, 16 Apr 2013 10:02:31 +0200	[thread overview]
Message-ID: <m2eheaaoo8.fsf@christianmoe.com> (raw)
In-Reply-To: <m2li8jueod.fsf@gmail.com>

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

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.


  reply	other threads:[~2013-04-16  8:00 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 [this message]
2013-04-16  8:23   ` Sebastien Vauban
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=m2eheaaoo8.fsf@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=guivho@gmail.com \


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