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


I am wondering why the default value of header argument :tangle is 'no'
rather than 'yes'.

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?

There are probably some very valid reasons why the default is 'no'
rather than 'yes'. Please enlighten me.



The older I grow, the more I distrust the
familiar doctrine that age brings wisdom.
		-- H. L. Mencken

             reply	other threads:[~2013-04-16  7:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16  7:18 Guido Van Hoecke [this message]
2013-04-16  8:02 ` why is 'no' the default value of :tangle Christian Moe
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=m2li8jueod.fsf@gmail.com \
    --to=guivho@gmail.com \
    --cc=emacs-orgmode@gnu.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).