From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ken Williams Subject: More specific LaTeX output classes Date: Fri, 2 Dec 2011 15:15:55 -0600 Message-ID: <21A5E1E970CD46459ECBE86D6CC4B28C52E23E0F@spexch01.WindLogics.local> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:48307) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RWaSd-0007Ai-AY for emacs-orgmode@gnu.org; Fri, 02 Dec 2011 16:16:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RWaSc-0002NK-16 for emacs-orgmode@gnu.org; Fri, 02 Dec 2011 16:15:59 -0500 Received: from shrimp.windlogics.com ([216.245.170.164]:23169) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RWaSb-0002N3-UI for emacs-orgmode@gnu.org; Fri, 02 Dec 2011 16:15:57 -0500 Content-Language: en-US List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "emacs-orgmode@gnu.org" 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 t= hat, a next step might be to provide nice defaults that do things like synt= ax-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 mis= sed it. =3D) -- Ken Williams, Senior Research Scientist WindLogics http://windlogics.com CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the inte= nded recipient(s) and may contain confidential and privileged information. = Any unauthorized review, use, disclosure or distribution of any kind is str= ictly prohibited. If you are not the intended recipient, please contact the= sender via reply e-mail and destroy all copies of the original message. Th= ank you.