From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [babel] Painless integration of source blocks with language
Date: Mon, 17 Jan 2011 09:18:56 -0700 [thread overview]
Message-ID: <87oc7fjy4n.fsf@gmail.com> (raw)
In-Reply-To: 80y66jvpwz.fsf@missioncriticalit.com
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
>> I've just pushed up a new header argument combination ":comments noweb"
>> which will wrap all embedded noweb sections in link comments, as
>> demonstrated in the following example. Hopefully this should be
>> sufficient for a complete mapping from a pure code file back to the
>> original org-mode file.
>
> If I understand correctly, this is some sort of enhancement to the ":comments
> yes" option.
>
> If yes, is there a reason to have both values, with subtle differences?
> Shouldn't we port the behavior of ":comments noweb" to the ":comments yes"
> value?
>
Yes, the reason to retain both variants is that in the case of short
noweb references embedded in a single line, e.g.
#+source: first
#+begin_src ruby
5
#+end_src
#+begin_src ruby :noweb yes
<<first>> + 6
#+end_src
the yes option would be preferable, as the insertion of comments around
the noweb reference would result in adding line breaks around the
reference and possibly breaking new-line sensitive code.
Cheers -- Eric
>
> Best regards,
> Seb
next prev parent reply other threads:[~2011-01-17 16:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 22:29 [babel] Painless integration of source blocks with language Seth Burleigh
2011-01-09 1:54 ` Eric Schulte
2011-01-09 9:40 ` Štěpán Němec
2011-01-09 17:59 ` Eric Schulte
2011-01-10 0:59 ` Seth Burleigh
2011-01-10 2:13 ` Eric Schulte
2011-01-10 3:49 ` Seth Burleigh
2011-01-10 4:01 ` Seth Burleigh
2011-01-11 17:00 ` Eric Schulte
2011-01-10 18:46 ` Eric S Fraga
2011-01-11 17:12 ` Eric Schulte
[not found] ` <AANLkTi=dNTn6HBeR4wV7039FDDyPGtmWbmL0biFwT-ta@mail.gmail.com>
2011-01-11 23:09 ` Seth Burleigh
2011-01-13 9:11 ` Eric S Fraga
2011-01-13 15:23 ` Seth Burleigh
2011-01-13 21:23 ` Eric Schulte
2011-01-13 23:44 ` Seth Burleigh
2011-01-16 15:31 ` Eric Schulte
2011-01-17 9:29 ` Sébastien Vauban
2011-01-17 16:18 ` Eric Schulte [this message]
2011-01-17 19:32 ` Sébastien Vauban
2011-01-17 22:15 ` Seth Burleigh
2011-01-17 22:44 ` Sébastien Vauban
2011-01-18 18:11 ` Seth Burleigh
2011-01-18 18:14 ` Seth Burleigh
2011-01-18 18:38 ` Seth Burleigh
2011-01-19 7:28 ` Eric Schulte
2011-01-24 14:49 ` Seth Burleigh
2011-01-18 19:53 ` Bastien
2011-01-24 11:56 ` Dan Davison
2011-01-24 18:56 ` Eric S Fraga
2011-01-26 10:43 ` Sébastien Vauban
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=87oc7fjy4n.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).