emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Allen S. Rout" <asr@ufl.edu>
To: emacs-orgmode@gnu.org
Subject: Is babel just ... unstable at the moment?
Date: Thu, 01 Mar 2012 11:00:15 -0500	[thread overview]
Message-ID: <jio6eg$ui2$1@dough.gmane.org> (raw)

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

             reply	other threads:[~2012-03-01 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 16:00 Allen S. Rout [this message]
2012-03-01 20:19 ` Is babel just ... unstable at the moment? Eric Schulte
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:

  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='jio6eg$ui2$1@dough.gmane.org' \
    --to=asr@ufl.edu \
    --cc=emacs-orgmode@gnu.org \


* 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


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