From mboxrd@z Thu Jan 1 00:00:00 1970 From: Liam Healy Subject: Re: Restore raw output in LaTeX export from in-line code block Date: Sun, 6 Oct 2013 10:28:31 -0400 Message-ID: References: <87mwmvqum2.fsf@gmail.com> <87haczol8i.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35739) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VSpKO-0001Zp-2z for emacs-orgmode@gnu.org; Sun, 06 Oct 2013 10:29:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VSpKH-0004J3-Kg for emacs-orgmode@gnu.org; Sun, 06 Oct 2013 10:29:00 -0400 Received: from mail-pd0-f173.google.com ([209.85.192.173]:62734) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VSpKH-0004Iu-E2 for emacs-orgmode@gnu.org; Sun, 06 Oct 2013 10:28:53 -0400 Received: by mail-pd0-f173.google.com with SMTP id p10so6027807pdj.18 for ; Sun, 06 Oct 2013 07:28:51 -0700 (PDT) In-Reply-To: <87haczol8i.fsf@gmail.com> 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: Eric Schulte Cc: Org-mode mailing list On Wed, Oct 2, 2013 at 9:28 AM, Eric Schulte wrote: > > > inline "\\sqrt{2}" works > > > Are you able to interactively execute inline code blocks? > > I'm not sure what the issue could be. > > Best, > Thanks for the response Eric. I do not get the results you do: src_lisp[:results raw]{(format nil "\\sqrt{2~c" (code-char 125))} gives me "$\backslash$\sqrt{2}" which is obviously wrong. Even so, what you get is wrong too; it should be \sqrt{2} (a single backslash and no quotes), which is what I get under 7.9.4. If I have only one backslash, src_lisp[:results raw]{(format nil "\sqrt{2~c" (code-char 125))} I get "sqrt\{2\}" still wrong. It appears there is more than one problem, and one of the problems is the Common Lisp's escaping of "\" with a second "\" is being misinterpreted. A possible second problem is that it seems to now use #'print (or the equivalent) on the lisp side instead of #'princ, so that the output includes escape characters. Thanks, Liam