emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org, Alan L Tyree <alantyree@gmail.com>,
	Rainer M Krug <r.m.krug@gmail.com>
Subject: Re: [babel] Commenting out src blocks for tangling
Date: Fri, 18 Oct 2013 16:37:07 +0200	[thread overview]
Message-ID: <m261su3ass.fsf@polytechnique.org> (raw)
In-Reply-To: <877glsg57i.fsf@bzg.ath.cx>

Hello,

Sorry to resurrect this old thread, but I cannot make this work.

bzg@altern.org writes:

> Rainer M Krug <r.m.krug@gmail.com> writes:
>
>> I agree - COMMENTing a subtree should automatically disable tangling of code blocks in the
>> subtree. Would this something which could be introduced easily, as it seems there are quite a few
>> who assumed that it would be doing it?
>
> This is now the case in master:
> http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=8e0b45

I just tried it with my init file and it did not work. Here is a
minimal example. Save this as "test.org":

--8<---------------cut here---------------start------------->8---
* Testing

#+BEGIN_SRC emacs-lisp
(message "hello world")
#+END_SRC

* COMMENT Commenting

#+BEGIN_SRC emacs-lisp
(message "Salut le monde 2")
#+END_SRC
--8<---------------cut here---------------end--------------->8---

Then do a "M-x org-babel-load-file" giving "test.org" as file name.

If you look at *Messages*, or at the generated test.el, you will see the
second block has been tangled.

Am I missing something with this feature, or is this a bug? (I tried
with "emacs -Q" and loading a current org, and the same happens.)

Thanks,

Alan

next prev parent reply	other threads:[~2013-10-18 14:37 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
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 [this message]
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=m261su3ass.fsf@polytechnique.org \
    --to=alan.schmitt@polytechnique.org \
    --cc=alantyree@gmail.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=r.m.krug@gmail.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

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