[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Orgmode] Re: org-export-sweave

From: Carsten Dominik
Subject: Re: [Orgmode] Re: org-export-sweave
Date: Thu, 18 Sep 2008 10:58:46 +0200

On Sep 17, 2008, at 8:44 PM, Austin Frank wrote:


Thanks for the response!

On Tue, Sep 16 2008, Carsten Dominik wrote:

since you want to include tis code literally into LaTeX,  the best is
probably to encapsulate it into


and to try to solve only the local editing issue.

Yes, this makes sense.  Though, since really all I need to do is wrap
source code written in R in a \LaTeX environment, I might also like to

#+LATEX:  \begin{Scode}
a <- 3
#+LATEX:  \end{Scode}

Take a look at the function org-edit-src-find-region-and-lang.  There
is a list of regular expressions that can be used to identify regions
that should be edited in special modes - maybe I can make this list
extensible - first, give it a try and see if you can get it working by
editing the list.

While I think opening up this list to customization is probably a good
idea, I could not get my new entries to behave the way I wanted.  The
problem, I suspect, may have to do with the ordering of the different
language environments.  Suppose I had

a <- 3

in an org file.  I guess that I want the code within the Scode
environment to me in r-mode, and the code outside of that but still
within the LATEX block to be in LaTeX-mode. In what order should these
two definitions appear within the re-list?

FWIW, attached is a patch of the setup I tried to use. When I hit C- c ' inside either of the above examples, I get a temporary buffer that's in
latex-mode.  I was hoping to get a temporary buffer in r-mode.  I also
tried a version of the code that used the same entries in the re-list,
but put them at the bottom, under the entries for ascii. Same results.

Thanks for any further advice,

diff --git a/lisp/org.el b/lisp/org.el
index 4b29704..0612653 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -5562,6 +5562,8 @@ the language, a switch telling of the content should be in a single line."
           ("^#\\+begin_example.*\n" "^#\\+end_example" "fundamental")
           ("^#\\+html:" "\n" "html" single-line)
           ("^#\\+begin_html.*\n" "\n#\\+end_html" "html")
+           ("^\\s*\\\\begin{scode}" "^\\s*\\\\end{scode}" "r")

These regular expressions are incorrect. \\s- is the way to denote whitespace. However, since hat also includes newlines, I prefer to write "[ \t]" in such cases.


- Carsten

+ ("^#\\+latex:\\s*\\\\begin{scode}" "^#\\+latex:\\s*\\\ \end{scode}" "r")
           ("^#\\+begin_latex.*\n" "\n#\\+end_latex" "latex")
           ("^#\\+latex:" "\n" "latex" single-line)
           ("^#\\+begin_ascii.*\n" "\n#\\+end_ascii" "fundamental")

Austin Frank
GPG Public Key (D7398C2F): http://aufrank.net/personal.asc
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]