emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Charles C. Berry" <ccberry@ucsd.edu>
To: daimrod <daimrod@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: bug in orgmode parsing of results
Date: Tue, 27 Dec 2016 10:11:55 -0800	[thread overview]
Message-ID: <alpine.OSX.2.20.1612271004350.729@charles-berrys-macbook.local> (raw)
In-Reply-To: <38887d7f-355f-65c4-b3f9-ab347780b9c4@gmail.com>

On Tue, 27 Dec 2016, daimrod wrote:

> Hi,
>
> I've found what I think is a bug in orgmode parsing.
> When the following file is parsed :
>
> * Test
> #+BEGIN_SRC emacs-lisp :exports results :results raw drawer
> (format "- Test2")
> #+END_SRC
>
> #+RESULTS:
> :RESULTS:
> - Test2
> :END:
>

[snip]

>
> That is, it generates a DRAWER, which seems correct.
>
> However, when the following file is parsed :
>
> * Test
> #+BEGIN_SRC emacs-lisp :exports results :results raw drawer
> (format "* Test2")
> #+END_SRC
>
> #+RESULTS:
> :RESULTS:
> * Test2
> :END:
>

[deleted]

> That is, it generates a PARAGRAPH which seems incorrect.
>
> WDYT?
>

What I think is that you should run org-lint on your document. It will say 
something like this (but with different line numbers):

   Line Trust Warning
      2 low   Forbidden combination in header ":results": raw, drawer
     12 low   Forbidden combination in header ":results": raw, drawer
     17 low   Possible incomplete drawer ":RESULTS:"

The last one should catch your eye.

If you want to generate results that have lines that start with `*' you 
need to protect them. A good way to do this is to wrap them in a src block 
or export block like this:

#+BEGIN_SRC emacs-lisp :exports results :wrap export latex
(format "* Test2")
#+END_SRC

HTH,

Chuck

  parent reply	other threads:[~2016-12-27 18:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-27 13:36 bug in orgmode parsing of results daimrod
2016-12-27 18:09 ` Nicolas Goaziou
2016-12-28 13:56   ` daimrod
2016-12-27 18:11 ` Charles C. Berry [this message]
2016-12-28 14:03   ` daimrod

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=alpine.OSX.2.20.1612271004350.729@charles-berrys-macbook.local \
    --to=ccberry@ucsd.edu \
    --cc=daimrod@gmail.com \
    --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).