emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jarmo Hurri <jarmo.hurri@iki.fi>
To: emacs-orgmode@gnu.org
Subject: Babel CALL no longer produces HTML output
Date: Sat, 23 Jul 2016 15:14:47 +0300	[thread overview]
Message-ID: <87r3akzh3c.fsf@iki.fi> (raw)


Greetings.

The Org example below used to work correctly when exported as HTML until
I pulled a newer version of Org from git. I am first going to include
the example here, and then explain the reasoning behind its structure.

=======================================================================
* Example
  
  This call here produced HTML output when exported as HTML until the
  newer versions of Org. Now it produces no HTML output whatsoever.

  #+CALL: rekursio-pystyviivat[:noweb yes]() :results html
  
  The following code blocks still work as expected.
  
  #+NAME: rekursio-pystyviivat-runko
  #+BEGIN_SRC processing :exports none
    if (viivoja == 0)
    return;

    line (x, 0, x, korkeus);
    piirraPystyviivat (viivoja - 1, x + 10, 0.9 * korkeus);
  #+END_SRC

  #+NAME: rekursio-pystyviivat
  #+BEGIN_SRC processing :exports code :noweb no
    void piirraPystyviivat (int viivoja, float x, float korkeus)
    {
      <<rekursio-pystyviivat-runko>>
    }

    void setup ()
    {
      size (600, 400);
      noLoop ();
    }

    void draw ()
    {
      piirraPystyviivat (50, 10, 350);
    }
  #+END_SRC
=======================================================================

In the example above I am playing with noweb to produce the following
_excellent_ teaching effect:

- the last Babel code block is what a student sees

- the student is supposed to replace
  <<rekursio-pystyviivat-runko>>
  with correct code, in this case the body of a recursive function

- the last block has ":noweb no" so that the missing part is not
  replaced by the correct solution

- in the CALL, however, noweb is set to yes so that noweb replacement is
  done, and the first block produces the correct output (in the case of
  Processing language, this is a picture)

I use this structure quite a bit in my material, which is finished
except for layout formatting. So I am going to be in trouble if I can no
longer get the logic to work in Org.

Jarmo

             reply	other threads:[~2016-07-23 12:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-23 12:14 Jarmo Hurri [this message]
2016-07-23 12:48 ` Babel CALL no longer produces HTML output Christian Moe
2016-07-23 13:03   ` Jarmo Hurri
2016-07-24 17:00     ` Christian Moe
2016-07-23 16:10 ` Charles C. Berry
2016-07-23 16:51   ` Nicolas Goaziou
2016-07-23 22:16     ` Charles C. Berry
2016-07-25  7:08       ` Nicolas Goaziou
2016-07-25  7:48         ` Thomas S. Dye
2016-07-25  8:01           ` Nicolas Goaziou
2016-07-25 15:55             ` Charles C. Berry
2016-07-25 17:27             ` Thomas S. Dye
2016-07-23 16:52   ` Jarmo Hurri

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=87r3akzh3c.fsf@iki.fi \
    --to=jarmo.hurri@iki.fi \
    --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).