From: Eric Schulte <eric.schulte@gmx.com>
To: "Allen S. Rout" <asr@ufl.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Is babel just ... unstable at the moment?
Date: Thu, 01 Mar 2012 13:19:36 -0700 [thread overview]
Message-ID: <87linkoyzr.fsf@gmx.com> (raw)
In-Reply-To: <jio6eg$ui2$1@dough.gmane.org> (Allen S. Rout's message of "Thu, 01 Mar 2012 11:00:15 -0500")
Hi Allen,
I think what you are experiencing is the lack of previous heavy usage of
inline call lines -- especially with multiple such calls on the same
line. You've discovered a couple of edge cases and you seem to have a
knack for coming up with pernicious examples.
Please do keep these sorts of error reports coming, as I would like to
fix any such errors in the code.
Thanks,
"Allen S. Rout" <asr@ufl.edu> writes:
> So I keep running into very strange babel behaviors.
>
> In addition to the whacked-out rendering oddities I've been posting
> about, I've just executed a static R block a half dozen times and
> gotten three or four different results blocks. I'm not going to try
> to minimal-example this one, it seems too timing sensitive to be worth
> attempting replication.
>
> I'm using the blocks-calling-other-blocks behavior rather heavily, and
> the variation seems to be that, on some calls, output from
> dependencies is just getting pasted into the output from the dependant
> block.
>
> Worse, there was one occasion on which it seems I got an output line
> from 'last' C-c C-c in 'this' run's output block.
>
> I've been seeing comments about changes to the babel block formats
> recently, so it's perhaps plausible that git HEAD just isn't
> stable. Should I back off?
>
>
> - Allen S. Rout
>
>
>
>
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2012-03-01 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 16:00 Is babel just ... unstable at the moment? Allen S. Rout
2012-03-01 20:19 ` Eric Schulte [this message]
2012-03-01 21:14 ` Allen S. Rout
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=87linkoyzr.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=asr@ufl.edu \
--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).