From mboxrd@z Thu Jan 1 00:00:00 1970 From: SabreWolfy Subject: Re: Guidance for preparing document with code Date: Wed, 29 May 2013 17:24:08 +0000 (UTC) Message-ID: References: <8738t5lq77.fsf@pierrot.dokosmarshall.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:54070) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uhk72-0002uH-7g for emacs-orgmode@gnu.org; Wed, 29 May 2013 13:24:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Uhk6v-0001FD-23 for emacs-orgmode@gnu.org; Wed, 29 May 2013 13:24:36 -0400 Received: from plane.gmane.org ([80.91.229.3]:47770) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uhk6u-0001F5-RY for emacs-orgmode@gnu.org; Wed, 29 May 2013 13:24:28 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Uhk6q-0004C5-C1 for emacs-orgmode@gnu.org; Wed, 29 May 2013 19:24:24 +0200 Received: from 41-135-53-181.dsl.mweb.co.za ([41.135.53.181]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 29 May 2013 19:24:24 +0200 Received: from sabrewolfy by 41-135-53-181.dsl.mweb.co.za with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 29 May 2013 19:24:24 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Nick Dokos gmail.com> writes: > org-babel is the right tool. Getting the headers right might involve > some fiddling: there have been many question on the ML about those so > you can try searching, but if after some effort you are still running > into a wall, just post what you have, what you want to accomplish and > how your purported solution fails: there are lots of people able and > willing to help. The only thing to keep in mind is that the shorter the > example, the better: don't post your 100-page org file; extract the > example(s) that you want help with. Thanks. Apologies -- I meant *headers* (ie: a structured/outline-type document), not *headings*. > If you are using the R code for your reference, and only presenting the > results, that's *not* literate programming: you don't have to worry > about the noweb stuff. > I wanted to include explanatory text, the R code, then the output of the code, all in the same document. The R code will not be relevant to the reader, but I'd like it included and executed to produce output.