all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Charles Berry <ccberry@ucsd.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Using :results output org with new exporter exporting as verbatim with LaTeX
Date: Sun, 24 Mar 2013 12:14:58 -0500	[thread overview]
Message-ID: <CA+M2ft-ujHmbuFFvR+rCRww7y2K6-0dC9zsvB1fPmtLh+eEyqQ@mail.gmail.com> (raw)
In-Reply-To: <loom.20130324T163700-393@post.gmane.org>

On Sun, Mar 24, 2013 at 11:00 AM, Charles Berry <ccberry@ucsd.edu> wrote:
> John Hendy <jw.hendy <at> gmail.com> writes:
>
> [deleted]
>
>> wrap [...] is non-existent in formal documentation from what I've seen
>
> It is in the manual:
>
>   14.8.2.23 `:wrap'
>
> See
>
>   http://orgmode.org/manual/wrap.html#wrap
>
> or from emacs:
>
>   C-h i m org RET C-s wrap RET RET

Ah. Forgive my denseness! I guess I'm just perplexed by what "level"
these options fall in. The suggestion was to use =:results output
wrap=, not :wrap (hence searching for that instead of just ":wrap".
:wrap gets it's own high level documentation page while the other
options used similarly (if =:results output wrap= is the right syntax)
seem to be considred "sub options" of something else:
- http://orgmode.org/manual/results.html#results

(Also note that =wrap= doesn't appear on that list, even though it
does work with :results output). On that note, is there a discernible
difference in practice between:

:wrap syntax:

#+begin_results
blah
#+end_results

and :results output wrap syntax:

:results:
blah
:end:

John


>
> HTH,
>
> Chuck
>
>

      reply	other threads:[~2013-03-24 17:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 23:05 Using :results output org with new exporter exporting as verbatim with LaTeX John Hendy
2013-03-23 22:12 ` Eric Schulte
2013-03-24  1:40   ` John Hendy
2013-03-24 16:00     ` Charles Berry
2013-03-24 17:14       ` John Hendy [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+M2ft-ujHmbuFFvR+rCRww7y2K6-0dC9zsvB1fPmtLh+eEyqQ@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=ccberry@ucsd.edu \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.