From: Eric Schulte <schulte.eric@gmail.com>
To: Neeum Zawan <mailinglists@nawaz.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Regression bug in tangle/weave
Date: Sun, 10 Jul 2011 09:46:10 -0600 [thread overview]
Message-ID: <87fwmeruyh.fsf@gmail.com> (raw)
In-Reply-To: 877h7rtoqn.fsf@fester.com
Neeum Zawan <mailinglists@nawaz.org> writes:
> Eric Schulte <schulte.eric@gmail.com> writes:
>
>> Hi,
>>
>> Indeed this example below no longer works, however I believe the new
>> behavior is both desired and permanent. I'll explain and include an
>> option for how your example could be restructured to work with the new
>> code.
>>
>> We ran into problems automatically removing trailing newlines from code
>> block bodies as in some languages (looking at you Python and Haskell)
>> things like trailing newlines are of syntactic importance. In your
>> example this behavior results in the insertion of newlines after
>> file-name and file-version. Babel is careful to preserve line prefixes
>> when expanding references in comments, so it then reproduces the
>>
>> # Generated from
>>
>> portion of that line for every line of the expanded noweb references.
>>
>> I would suggest the following alternatives, either using a data
>> references in stead of a code block reference as in the file-version
>> example below, or using an evaluated code block as in the file-name
>> example below. Hope this helps.
>
> Oh dear. Am I to blame for this?
>
> When I reported the newline issue, somewhere in the back of my mind I
> knew it probably would have some ugly consequences. Now I see them.
>
> An evaluated code block seems inelegant/confusing if one intends to
> export that code as part of the document. A data reference seems OK, but
> I take it you can't have references within it?
>
> Unfortunately, I see no easy solution...
>
In these cases, I feel that a data reference is the simplest, most
natural solution, and lightest-syntax solution in these cases, and I
don't see it as an ugly compromise. Just my opinion.
As I mentioned above I feel that the current behavior is both desired
and permanent, and I'm happy that you raised the newline issue that help
lead to this behavior.
Best -- Eric
--
Eric Schulte
http://cs.unm.edu/~eschulte/
prev parent reply other threads:[~2011-07-10 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 15:24 Regression bug in tangle/weave MidLifeXis at PerlMonks
2011-06-30 18:30 ` Eric Schulte
2011-07-01 12:51 ` MidLifeXis at PerlMonks
2011-07-01 19:14 ` Eric Schulte
2011-07-01 20:40 ` MidLifeXis at PerlMonks
2011-07-01 21:36 ` Eric Schulte
2011-07-05 12:56 ` MidLifeXis at PerlMonks
2011-07-05 15:17 ` Eric Schulte
2011-07-09 16:14 ` Neeum Zawan
2011-07-10 15:46 ` Eric Schulte [this message]
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=87fwmeruyh.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mailinglists@nawaz.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).