From: Chris Gray <chrismgray@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Org-mode version 6.31trans; Exporting src blocks to LaTeX produces .tex file that fails to compile
Date: Fri, 02 Oct 2009 11:36:47 +0200 [thread overview]
Message-ID: <86ocoq16j4.fsf@portan.ibr.cs.tu-bs.de> (raw)
In-Reply-To: 86iqeyfba3.fsf@portan.ibr.cs.tu-bs.de
Hi,
The problem was with my org-special-blocks contrib package. The
attached patch fixes it. Sorry for the noise.
Cheers,
Chris
commit 4d327b5f1e80ea0e493aa70d09c53042216a1390
Author: Chris Gray <chrismgray@gmail.com>
Date: Fri Oct 2 11:31:21 2009 +0200
Added a variable to ignore some blocks.
Modified contrib/lisp/org-special-blocks.el
diff --git a/contrib/lisp/org-special-blocks.el b/contrib/lisp/org-special-blocks.el
index b8ce4d5..af50b30 100644
--- a/contrib/lisp/org-special-blocks.el
+++ b/contrib/lisp/org-special-blocks.el
@@ -40,17 +40,23 @@
;; user to add this class to his or her stylesheet if this div is to
;; mean anything.
+(defvar org-special-blocks-ignore-regexp "^\\(LaTeX\\|HTML\\)$"
+ "A regexp indicating the names of blocks that should be ignored
+by org-special-blocks. These blocks will presumably be
+interpreted by other mechanisms.")
+
(defun org-special-blocks-make-special-cookies ()
"Adds special cookies when #+begin_foo and #+end_foo tokens are
seen. This is run after a few special cases are taken care of."
(when (or htmlp latexp)
(goto-char (point-min))
(while (re-search-forward "^#\\+\\(begin\\|end\\)_\\(.*\\)$" nil t)
- (replace-match
- (if (equal (downcase (match-string 1)) "begin")
- (concat "ORG-" (match-string 2) "-START")
- (concat "ORG-" (match-string 2) "-END"))
- t t))))
+ (unless (string-match-p org-special-blocks-ignore-regexp (match-string 2))
+ (replace-match
+ (if (equal (downcase (match-string 1)) "begin")
+ (concat "ORG-" (match-string 2) "-START")
+ (concat "ORG-" (match-string 2) "-END"))
+ t t)))))
(add-hook 'org-export-preprocess-after-blockquote-hook
'org-special-blocks-make-special-cookies)
Chris Gray wrote:
> Eric Schulte wrote:
> Hi Eric,
>> I tried to recreate this problem but was unable to do so on my
>> computer. To recreate I exported
>> #+srcname: determine the neighbors of the segments that the bisector hits
>> #+begin_src lua :tangle no :exports code
>> local s1, s2 = intersecting_segs[1], intersecting_segs[2]
>> local n1 = table_find_segment(cell.neighbors, s1)
>> local n2 = table_find_segment(cell.neighbors, s2)
>> #+end_src
>> with my personal Emacs configuration and I got the following in the
>> resulting .tex file
>> #+begin_example
>> \lstset{language=lua}
>> \begin{lstlisting}
>> local s1, s2 = intersecting_segs[1], intersecting_segs[2]
>> local n1 = table_find_segment(cell.neighbors, s1)
>> local n2 = table_find_segment(cell.neighbors, s2)
>> \end{lstlisting}
>> #+end_example
> Are you exporting to LaTeX or some intermediate org-based format? I am
> just using C-c C-e L to export. Should I be using an org-babel command?
>> note that Org-babel shouldn't have any effect here as it currently
>> doesn't recognize the lua language.
> Sorry, I should have been more clear about that. I have added the
> following to my setup.
> (org-babel-add-interpreter "lua")
> (add-to-list 'org-babel-tangle-langs '("lua" "lua" "#!/usr/bin/env lua"))
>> Sorry I can't be of more help. Maybe try with emacs -Q and
>> incrementally add your personal configuration until the problem
>> re-appears.
> Will do.
> Cheers,
> Chris
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
--
next prev parent reply other threads:[~2009-10-02 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 16:18 Org-mode version 6.31trans; Exporting src blocks to LaTeX produces .tex file that fails to compile cgray
2009-10-01 19:49 ` Eric Schulte
2009-10-02 8:30 ` Chris Gray
2009-10-02 9:36 ` Chris Gray [this message]
2009-10-02 10:04 ` Carsten Dominik
2009-10-02 10:45 ` Chris Gray
2009-10-02 11:12 ` Carsten Dominik
2009-10-02 15:11 ` Eric Schulte
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ocoq16j4.fsf@portan.ibr.cs.tu-bs.de \
--to=chrismgray@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.