emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer@krugs.de (Rainer M. Krug)
To: Christian Moe <mail@christianmoe.com>
Cc: emacs-orgmode@gnu.org, Bill White <billw@wolfram.com>
Subject: Re: disable tangling for an entire section?
Date: Mon, 13 May 2013 10:23:00 +0200	[thread overview]
Message-ID: <87txm7mgpn.fsf@krugs.de> (raw)
In-Reply-To: <m2sj1wzluc.fsf@uio.no> (Christian Moe's message of "Thu, 09 May 2013 08:54:03 +0200")

Christian Moe <mail@christianmoe.com> writes:

>> I was hoping that a higher-level setting would override all tangle
>> settings under it, no matter what they might be.  This would make it
>> possible to change an entire section's tangling without fussing with
>> each code block's setting.
>
> The status quo makes more sense, I think. It allows you to easily change
> an entire section's tangling but make specific exceptions that
> override the general setting.

I agree with Christian here. But you could trick org into achieving what
you want, in specifying a tangle target in the PROPERTIES sectio, given
that you only use :tangle yes :

* headline
:PROPERTIES:
:tangle:   tmp.tmp
:END:

#+begin_src perl :tangle yes
2 + 2
#+end_src
#+begin_src perl :tangle no
3 + 3
#+end_src
 

In this case, the the first code block can be tangled into tmp.tmp and
the second one won't. So no harm done to your "clean" tangled file, only
the tmp.tmp, which you can discard afterwords.

Cheers,

Rainer

>
> Yours,
> Christian
>


-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :       +33 - (0)9 53 10 27 44
Cell:       +33 - (0)6 85 62 59 98
Fax :       +33 - (0)9 58 10 27 44

Fax (D):    +49 - (0)3 21 21 25 22 44

email:      Rainer@krugs.de

Skype:      RMkrug

  reply	other threads:[~2013-05-13  8:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07  5:47 disable tangling for an entire section? Bill White
2013-05-07  7:14 ` Christian Moe
2013-05-07 12:23   ` Sebastien Vauban
2013-05-08 17:00     ` Bill White
2013-05-09  6:54       ` Christian Moe
2013-05-13  8:23         ` Rainer M. Krug [this message]
2013-05-13 15:51           ` Bill White

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=87txm7mgpn.fsf@krugs.de \
    --to=rainer@krugs.de \
    --cc=billw@wolfram.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@christianmoe.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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