emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Ken Williams <Ken.Williams@windlogics.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: More specific LaTeX output classes
Date: Fri, 2 Dec 2011 15:15:55 -0600	[thread overview]
Message-ID: <21A5E1E970CD46459ECBE86D6CC4B28C52E23E0F@spexch01.WindLogics.local> (raw)

If I export the following code to LaTeX:

--------------------------
#+begin_src R
CV.t.hat <- rowMeans(loss)[m]
CV.t.hat
#+end_src

#+results:
: [1] 1.135857
--------------------------

, then it looks like this in the *.tex file:

--------------------------
\begin{verbatim}
CV.t.hat <- rowMeans(loss)[m]
CV.t.hat
\end{verbatim}

\begin{verbatim}
 [1] 1.135857
\end{verbatim}
--------------------------

So there's no distinction between input & output, nor between various types of input (e.g. different programming languages).

Would it be possible for the export process to define various classes that default to being exactly like 'verbatim', but could be customized?  After that, a next step might be to provide nice defaults that do things like syntax-highlighting (through the 'minted' package, perhaps), or at least add a visual marker distinguishing between input & output.

Or of course it's possible some of this is already implemented and I've missed it. =)

--
Ken Williams, Senior Research Scientist
WindLogics
http://windlogics.com



CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of any kind is strictly prohibited. If you are not the intended recipient, please contact the sender via reply e-mail and destroy all copies of the original message. Thank you.

next             reply	other threads:[~2011-12-02 21:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 21:15 Ken Williams [this message]
2011-12-02 21:55 ` More specific LaTeX output classes Niels Giesen
2011-12-02 23:40   ` Nick Dokos

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=21A5E1E970CD46459ECBE86D6CC4B28C52E23E0F@spexch01.WindLogics.local \
    --to=ken.williams@windlogics.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

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).