emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: [PATCH] Protect active characters such as `~' when exporting to LaTeX
Date: Fri, 16 Jan 2015 15:58:33 +0100	[thread overview]
Message-ID: <86vbk63h7q.fsf@example.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 393 bytes --]

Hello,

When ~code~ is converted to LaTeX, it becomes \verb~code~; i.e., it uses
a potentially "dangerous" character, in this case `~' which is active.

In most cases, it is unnoticeable, but in some environments, it breaks.

The solution is to protect the command, what the attached patch does.

PS- Nicolas, can you apply this one without problem?

Best regards,
  Seb

-- 
Sebastien Vauban

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0002-Protect-active-characters-such-as.patch --]
[-- Type: text/x-patch, Size: 1143 bytes --]

From e5a6525898a41a4e4381c46575f7c54e8a367700 Mon Sep 17 00:00:00 2001
From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
Date: Fri, 16 Jan 2015 15:53:40 +0100
Subject: [PATCH] Protect active characters such as `~'

---
 lisp/ox-latex.el | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el
index 66cc6c2..cb6d75c 100644
--- a/lisp/ox-latex.el
+++ b/lisp/ox-latex.el
@@ -1,6 +1,6 @@
 ;;; ox-latex.el --- LaTeX Back-End for Org Export Engine

-;; Copyright (C) 2011-2014 Free Software Foundation, Inc.
+;; Copyright (C) 2011-2015 Free Software Foundation, Inc.

 ;; Author: Nicolas Goaziou <n.goaziou at gmail dot com>
 ;; Keywords: outlines, hypermedia, calendar, wp
@@ -1122,7 +1122,7 @@ INFO is a plist used as a communication channel.  See
      ;; and use "\\verb" command.
      ((eq 'verb fmt)
       (let ((separator (org-latex--find-verb-separator text)))
-	(concat "\\verb" separator
+	(concat "\\protect\\verb" separator
 		(replace-regexp-in-string "\n" " " text)
 		separator)))
      ;; Handle the `protectedtexttt' special case: Protect some
--
2.1.1

             reply	other threads:[~2015-01-16 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 14:58 Sebastien Vauban [this message]
2015-01-16 16:42 ` [PATCH] Protect active characters such as `~' when exporting to LaTeX Nick Dokos
2015-01-16 17:12 ` Aaron Ecay

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=86vbk63h7q.fsf@example.com \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).