emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thomas Alexander Gerds <tag@biostat.ku.dk>
To: emacs-orgmode@gnu.org
Subject: export of src block ignores :results
Date: Thu, 29 Sep 2016 08:42:07 +0200	[thread overview]
Message-ID: <87r383ky0w.fsf@biostat.ku.dk> (raw)

Hi

org's development version (I am using the one updated yesterday: 2b22d50
Nicolas Go 2016-09-28) seems to ignore the :results setting of a src
block. more specifically, the export of this

#+BEGIN_SRC R  :results output :exports code  :session *R* :cache yes 
2+2
#+END_SRC

#+RESULTS[<2016-09-29 08:32:48> e8e7ff579309fc6cacb1e75a0c1c671366c2eaf8]:
: [1] 4

should *not* include the results, but it does.  the elpa version, e.g.,
org-20160509, respects the :results setting. I tried to debug, but could
not find the place in the process where the option :results is
interpreted. here is how far I got: in the development version the
result of the function org-element-parse-buffer does include the result
of the src block "4" whereas in the elpa version result of the function
org-element-parse-buffer does include it.

did I miss something or is this a bug?

thanks, 
Thomas

-- 
sent from nil

             reply	other threads:[~2016-09-29  6:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29  6:42 Thomas Alexander Gerds [this message]
2016-09-29 16:25 ` export of src block ignores :results Charles C. Berry
2016-09-29 19:53   ` Thomas Alexander Gerds
2016-09-29 21:02     ` Charles C. Berry
2016-09-30  3:39       ` Charles C. Berry
2016-09-30  5:06         ` Thomas Alexander Gerds
2016-09-30 17:05           ` Charles C. Berry
2016-10-01  5:46             ` Thomas Alexander Gerds
2016-10-01 16:32               ` Charles C. Berry
2016-10-02 11:08                 ` Thomas Alexander Gerds
2016-10-01  8:37         ` Nicolas Goaziou
  -- strict thread matches above, loose matches on Subject: below --
2016-09-29  6:43 Thomas Alexander Gerds

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=87r383ky0w.fsf@biostat.ku.dk \
    --to=tag@biostat.ku.dk \
    --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).