From: Rainer M Krug <r.m.krug@gmail.com>
To: Sebastien Vauban
<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>,
emacs-orgmode <emacs-orgmode@gnu.org>, Bastien <bzg@gnu.org>
Subject: Re: [babel] Commenting out src blocks for tangling
Date: Thu, 28 Feb 2013 13:30:35 +0100 [thread overview]
Message-ID: <512F4DEB.7050202@gmail.com> (raw)
In-Reply-To: <86y5e87osz.fsf@somewhere.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 28/02/13 10:47, Sebastien Vauban wrote:
> Hi Rainer,
>
> Rainer M Krug wrote:
>> On 28/02/13 10:30, Sebastien Vauban wrote:
>>> Bastien wrote:
>>>> Rainer M Krug <r.m.krug-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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
>>>
>>> Does it work as well for the `:noexport:' tag?
>>
>> I don't think it should. Tangling is something different to export, so there should not be ay
>> interactions between the two in this respect. On the other hand, COMMENT is generic - it is a
>> COMMENT and does not concern anything. So it is applicable for tangling as well.
>>
>> I would actually say it would be counterintuitive if :noexport: would influence tangling as
>> it is governed by a completely different approach in org as well as in what I am doing with
>> the org file.
>
> I've always used :noexport: instead of COMMENT (as I hate the visual clutter of that wide
> keyword). So, for me, they were equivalent.
Follow up: would it be possible to have the same mechanism for tangling, i.e. a tag :notangle:?
functioning would be equivalent to property tangle: no but more visible and consistent with the
:noexport:? One could also define properties to be tangled and not tangled for different scenarios?
Rainer
>
> You must be right, though, that they aren't: COMMENT seems more generic than just export. So,
> dismiss my request.
>
> Best regards, Seb
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJRL03rAAoJENvXNx4PUvmCsGQIAKlPTGJzSlRSvPamZCs2XZqp
kR6YIU20QdSLs3Eei7p1VAFTdb4i9Ci6GaX8LfmForM4jrmkUYPqGNFHOl6Q6rwq
tCSCxAhIvEWZirs1tmhvj+jIZ2so61LTudMfzToEXPcowoCJXOzjS4GVb/QAysmX
qYrY/5OlEw7Qj8YlkmDoeTep4HtSKM941po1VWxm4AJPiyFkipgiQJ3bpVTq5g4p
/QIoG7QhNug1kstDx/2LfTXMZMU1zamBS1T5i0rzYHSkpoZwHCAjozXHtpNeW5VB
UOJTTctGNERb7sk70SM5ACoQxNne3Ojd5iQdjj+lJf0gKGbz20kT6rHrXUS7d9g=
=ryTy
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-02-28 12:55 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 [this message]
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=512F4DEB.7050202@gmail.com \
--to=r.m.krug@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.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).