emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan L Tyree <alantyree@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] Commenting out src blocks for tangling
Date: Thu, 28 Feb 2013 06:18:45 +1100	[thread overview]
Message-ID: <87mwup8t0q.fsf@breezy.my.home> (raw)
In-Reply-To: <87r4k18wy2.fsf@ucl.ac.uk>


Eric S Fraga writes:

> Hello,
>
> I finally bit the bullet and converted by rather convoluted and long
> emacs startup code to an org file with emacs-lisp code blocks.  I then
> tangle these into the actual code which is loaded by emacs at
> startup.  So far, so good, and it does make it easier for me to navigate
> around my customisations.
>
> However, it has highlighted a feature which is missing (I think) but
> which would be great.  I tangle all the code blocks to the same
> file.  It would be great if I could have the =org-babel-tangle= command
> skip sections that are COMMENTed out (i.e. headline with COMMENT, as
> produced by =org-toggle-comment=).
>
> Alternatively, a :nobabel: or :notangle: tag to mark subtrees that
> should be excluded would be fine.
>
> If I have missed a way of doing this, please do let me know (politely
> ;-).  If not, any suggestions on how to achieve this would be great.
G'day Eric,

If I understand your problem correctly, doesn't the property :tangle: do
what you want?

Cheers,
Alan

>
> Thanks,
> eric


-- 
Alan L Tyree           http://www2.austlii.edu.au/~alan
Tel:  04 2748 6206     sip:172385@iptel.org

  parent reply	other threads:[~2013-02-27 19:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27 17:53 [babel] Commenting out src blocks for tangling Eric S Fraga
2013-02-27 18:10 ` Aaron Ecay
2013-02-27 18:22   ` Eric S Fraga
2013-02-27 19:18 ` Alan L Tyree [this message]
2013-02-27 19:32   ` Eric S Fraga
2013-02-27 23:33     ` Darlan Cavalcante Moreira
2013-02-28  9:01       ` Rainer M Krug
2013-02-28  9:25         ` Bastien
2013-02-28  9:27           ` Rainer M Krug
2013-02-28  9:30           ` Sebastien Vauban
2013-02-28  9:42             ` Rainer M Krug
2013-02-28  9:47               ` Sebastien Vauban
2013-02-28 12:30                 ` Rainer M Krug
2013-03-02 10:31                   ` Bastien
2013-03-03  3:44                     ` Charles Berry
2013-03-03  6:18                       ` Bastien
2013-02-28  9:44             ` Bastien
2013-02-28  9:51           ` Rasmus
2013-02-28 10:05             ` Bastien
2013-02-28 19:45           ` Eric S Fraga
2013-10-18 14:37           ` Alan Schmitt
2013-10-18 16:43             ` Eric Schulte
2013-10-19  6:06               ` Alan Schmitt
2013-10-19 21:56                 ` Eric Schulte
2013-10-20 17:05                   ` Alan Schmitt
2013-10-20 21:58                     ` Eric Schulte
2013-10-21  6:49                       ` Alan Schmitt

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=87mwup8t0q.fsf@breezy.my.home \
    --to=alantyree@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    /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).