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

From: tsd@tsdye.com (Thomas S. Dye)
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Nicolas Goaziou <n.goaziou@gmail.com>, Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Bug in export of call lines
Date: Mon, 10 Mar 2014 16:45:19 -1000	[thread overview]
Message-ID: <m2k3c1v4g0.fsf@tsdye.com> (raw)
In-Reply-To: <87k3c2vts2.fsf@gmail.com> (Eric Schulte's message of "Mon, 10 Mar 2014 11:38:05 -0600")

Eric Schulte <schulte.eric@gmail.com> writes:

> Somehow this doesn't seem to be a problem with other languages, so I
> believe the necessary fix may be R specific.

Following is a small test that appears to indicate that the bug is R
specific and only bites when the source code block has :results raw.

  #+DATE: \today
  #+LATEX_CLASS: article
  #+LATEX_CLASS_OPTIONS:
  #+LATEX_HEADER:
  #+LATEX_HEADER_EXTRA:


  * Export this subtree to LaTeX
    :PROPERTIES:
    :results:  raw
    :END:

  Will lisp-2 export call_lisp-2() with a newline?

  Will python-2 export call_python-2() with a newline?

  Will r-2 export call_r-2() with a newline?

  Will lisp-2-raw export call_lisp-2-raw() with a newline?

  Will python-2-raw export call_python-2-raw() with a newline?

  Will r-2-raw export call_r-2-raw() with a newline?

  * Similar code in three languages

  #+name: lisp-2
  #+begin_src lisp
  (+ 1 1)
  #+end_src

  #+name: python-2
  #+begin_src python
  return(1 + 1)
  #+end_src

  #+name: r-2
  #+begin_src R
  1 + 1
  #+end_src

  #+name: lisp-2-raw
  #+begin_src lisp :results raw
  (+ 1 1)
  #+end_src

  #+name: python-2-raw
  #+begin_src python :results raw
  return(1 + 1)
  #+end_src

  #+name: r-2-raw
  #+begin_src R :results raw
  1 + 1
  #+end_src

Here is the relevant portion of the LaTeX export:

  Will lisp-2 export 2 with a newline?

  Will python-2 export 2 with a newline?

  Will r-2 export 2 with a newline?

  Will lisp-2-raw export 2 with a newline?

  Will python-2-raw export 2 with a newline?

  Will r-2-raw export 2
   with a newline?
  % Emacs 24.3.1 (Org mode 8.2.5h)

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

next prev parent reply	other threads:[~2014-03-11  2:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07  2:05 Bug in export of call lines Thomas S. Dye
2014-03-10 12:16 ` Nicolas Goaziou
2014-03-10 17:14   ` Thomas S. Dye
2014-03-10 17:38     ` Eric Schulte
2014-03-11  2:45       ` Thomas S. Dye [this message]
2014-03-11 13:23         ` Eric Schulte
2014-03-11 21:50           ` Thomas S. Dye
2014-03-12  1:40             ` Eric Schulte
2014-03-12  6:00               ` Thomas S. Dye

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=m2k3c1v4g0.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    --cc=schulte.eric@gmail.com \
    /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).