emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: Liam Healy <lnp@healy.washington.dc.us>
Cc: Org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Restore raw output in LaTeX export from in-line code block
Date: Sun, 29 Sep 2013 13:46:13 -0600	[thread overview]
Message-ID: <87mwmvqum2.fsf@gmail.com> (raw)
In-Reply-To: <CADe9tL6vqrGC0ru=+S3_yM82yHCP8KVs9hDQaRdq3J9ohnE2DQ@mail.gmail.com> (Liam Healy's message of "Sat, 28 Sep 2013 15:19:23 -0400")

Liam Healy <lnp@healy.washington.dc.us> writes:

> I noticed that raw results from in-line code blocks were disappearing in
> the new LaTeX exporter, and bisected the repo to the change 7117ad4f92. I
> have created the attached patch to fix the problem and restore the previous
> behavior.
>
> example file
>       * Test
>         1. Inline common lisp raw: src_lisp[:results raw]{(+ 2 2)}, should
> say 4.
>
>
> Desired output, restored by patch
>   \item Inline common lisp raw: 4, should say 4.
> Output without patch
>    \item Inline common lisp raw: , should say 4.
>
> If this looks right, please apply.
>
> Liam
>

Hi Liam,

You're actually noticing a symptom of an error in the way lisp code
blocks were handling results (conflating the output/results and the
scalar/vector distinction).  I've just pushed up a fix, please let me
know if you continue to see these types of errors.

Best,

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D

  reply	other threads:[~2013-09-29 19:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-28 19:19 Restore raw output in LaTeX export from in-line code block Liam Healy
2013-09-29 19:46 ` Eric Schulte [this message]
2013-10-01 23:36   ` Liam Healy
2013-10-02 13:28     ` Eric Schulte
2013-10-06 14:28       ` Liam Healy

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=87mwmvqum2.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=lnp@healy.washington.dc.us \
    /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).