emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Liam Healy <lnp@healy.washington.dc.us>
To: Org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Restore raw output in LaTeX export from in-line code block
Date: Sat, 28 Sep 2013 15:19:23 -0400	[thread overview]
Message-ID: <CADe9tL6vqrGC0ru=+S3_yM82yHCP8KVs9hDQaRdq3J9ohnE2DQ@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 539 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 663 bytes --]

[-- Attachment #2: 0001-Restore-raw-output-in-LaTeX-export-from-in-line-code.patch --]
[-- Type: application/octet-stream, Size: 1037 bytes --]

From 4d56221f954346b95f0cf0f23969c88f419b4705 Mon Sep 17 00:00:00 2001
From: "Liam M. Healy" <lhealy@common-lisp.net>
Date: Sat, 28 Sep 2013 13:17:53 -0400
Subject: [PATCH] Restore raw output in LaTeX export from in-line code block

Commit 7117ad4f92 caused the :results raw to produce empty output, e.g.
* Test
  1. Inline common lisp raw: src_lisp[:results raw]{(+ 2 2)}, should say 4.
produced the LaTeX line
   \item Inline common lisp raw: , should say 4.
This patch restores previous behavior, so that the LaTeX
   \item Inline common lisp raw: 4, should say 4.
---
 lisp/ob-core.el |    1 -
 1 file changed, 1 deletion(-)

diff --git a/lisp/ob-core.el b/lisp/ob-core.el
index a7c227b..472f9ea 100644
--- a/lisp/ob-core.el
+++ b/lisp/ob-core.el
@@ -2724,7 +2724,6 @@ Emacs shutdown."))
 		 (member "code" ,params)
 		 (member "pp" ,params)
 		 (and (or (member "output" ,params)
-			  (member "raw"    ,params)
 			  (member "org"    ,params)
 			  (member "drawer" ,params))
 		      (not (member "table" ,params))))
-- 
1.7.9.5


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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-28 19:19 Liam Healy [this message]
2013-09-29 19:46 ` Restore raw output in LaTeX export from in-line code block Eric Schulte
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='CADe9tL6vqrGC0ru=+S3_yM82yHCP8KVs9hDQaRdq3J9ohnE2DQ@mail.gmail.com' \
    --to=lnp@healy.washington.dc.us \
    --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 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).