emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Error with :wrap org in babel and 8.0-pre
Date: Mon, 15 Apr 2013 12:59:55 -0500	[thread overview]
Message-ID: <CA+M2ft8x1w=X5OPp4JvcY_S_fpaW4R5eyZg5BS+Jh=RDCKe2Tg@mail.gmail.com> (raw)
In-Reply-To: <87li8ncqzq.fsf@gmail.com>

On Fri, Apr 12, 2013 at 5:24 PM, Eric Schulte <schulte.eric@gmail.com> wrote:
> John Hendy <jw.hendy@gmail.com> writes:
>
>> I thought this was the proper syntax for printing stuff directly to a
>> LaTeX document:
>>
>> #+begin_src R :session :exports results :results output :wrap org
>>
>
> I think you want either ":results latex" or ":wrap latex".
>

Trying my best to follow the evolution here.... I've tried to discern
from the manual and Worg the best way to do something, generally try
it and fail. Then I post to the list and get an answer. A short time
later, I try doing what I think is approximately the same thing to
find that it seems to have changed since the last time:

To print multiple file names and =#+attr_stuff= options, the answer
was =:results output org :exports results=
- http://lists.gnu.org/archive/html/emacs-orgmode/2012-08/msg01224.html

Trying to do the same exact thing a bit later was =:results output
wrap=, shortly followed up with the instruction to use =:wrap org=
- http://lists.gnu.org/archive/html/emacs-orgmode/2013-03/msg01599.html

Now, it's =:wrap latex=, but I'm not sure why.

Is =:wrap org= appropriate for anything? I understood it as telling
Org-mode, "Hey, I want you to parse this results block as if it was
written directly in Org-mode." That seems like what I want to do.

Since I posted this question, I decided it would be easier to display
results in a small table. Something like this:

#+begin_src R :session r :exports results :results output :wrap org

library(ascii)

cat("Blah blah blah and this value is", var1,  "\n")

qty_table <- ascii(qtys[, c(1, 3, 4)], header = T, include.colnames =
T, include.rownames = F)

print(qty_table, type = "org")

#+end_src

That exports correctly (get my paragraphs and LaTeX table), but I
still get an error about \begin{org}. Using =:wrap latex= does not
work, as it's not interpreting the Org table properly.


Thanks for the assistance,
John

P.S. Sorry for the "venty" tone... I just hate 1) pestering the list
again and again for what I think are similar things and feeling
foolish and defeated by the documentation, and 2) having to wait to
have mysteries unveiled... especially when I'm using Org for
time-critical work things!

> Cheers,
>
>>
>> I've got a statement interspersing some prose with variable values like so:
>>
>> cat("This and such value was," var1, ", and this one was", var2, ".\n")
>>
>> The results block looks fine, but LaTeX is spitting out \begin{org}
>> and \end{org} around it, which results in a compilation error:
>>
>> ! LaTeX Error: Environment org undefined.
>>
>> See the LaTeX manual or LaTeX Companion for explanation.
>> Type  H <return>  for immediate help.
>>  ...
>>
>> l.51 \begin{org}
>>
>>
>> ! LaTeX Error: \begin{document} ended by \end{org}.
>>
>> Suggestions?
>>
>>
>> Thanks,
>> John
>>
>
> --
> Eric Schulte
> http://cs.unm.edu/~eschulte

  reply	other threads:[~2013-04-15 18:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 22:45 Error with :wrap org in babel and 8.0-pre John Hendy
2013-04-12 22:24 ` Eric Schulte
2013-04-15 17:59   ` John Hendy [this message]
2013-04-15 18:12     ` Eric Schulte
2013-04-15 19:35       ` John Hendy
2013-04-15 19:48         ` Andreas Leha
2013-04-15 19:52           ` John Hendy
2013-04-15 19:56         ` Eric Schulte
2013-04-15 19:56         ` Nicolas Goaziou
2013-04-15 20:05           ` John Hendy
2013-04-15 20:15             ` Nicolas Goaziou
2013-04-15 20:28               ` Eric Schulte
2013-04-15 20:51                 ` Sebastien Vauban
2013-04-15 21:29                   ` John Hendy
2013-04-15 21:44                     ` Sebastien Vauban
2013-04-15 21:51                       ` John Hendy
2013-04-15 21:24                 ` John Hendy
2013-04-15 21:42                   ` Sebastien Vauban
2013-04-15 22:38                   ` Eric Schulte
2013-04-15 22:48                     ` John Hendy
2013-04-15 23:27                       ` Eric Schulte
2013-04-15 23:56                         ` Thomas S. Dye
2013-04-16  2:37                           ` Eric Schulte
2013-04-16  7:58                         ` Sebastien Vauban
2013-04-16  8:23                         ` Christian Moe
2013-04-16 14:58                           ` John Hendy
2013-04-16 15:24                             ` Eric Schulte
2013-04-16 21:06                             ` Christian Moe
2013-04-15 20:09           ` Sebastien Vauban
2013-04-15 20:22             ` Nicolas Goaziou
2013-04-15 19:47       ` Sebastien Vauban
2013-04-15 21:38         ` John Hendy

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='CA+M2ft8x1w=X5OPp4JvcY_S_fpaW4R5eyZg5BS+Jh=RDCKe2Tg@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.com \
    /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).