From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Schmitt Subject: emphasis borders, double quotes, and export Date: Fri, 28 Mar 2014 14:58:08 +0100 Message-ID: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38753) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WTXIb-00056E-P6 for emacs-orgmode@gnu.org; Fri, 28 Mar 2014 09:58:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WTXIU-0005Hj-A6 for emacs-orgmode@gnu.org; Fri, 28 Mar 2014 09:58:21 -0400 Received: from mx1.polytechnique.org ([129.104.30.34]:49706) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WTXIU-0005HT-3M for emacs-orgmode@gnu.org; Fri, 28 Mar 2014 09:58:14 -0400 Received: from top-wifi (gue01.insa-rennes.fr [193.52.94.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id 772761408EEED for ; Fri, 28 Mar 2014 14:58:11 +0100 (CET) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode Hello, I have removed the single and double quote characters from my configuration of the emphasis borders: #+begin_src emacs-lisp (setcar (nthcdr 2 org-emphasis-regexp-components) " \t\n,") (custom-set-variables `(org-emphasis-alist ',org-emphasis-alist)) #+end_src However, the latex export of the following file is not correct. --8<---------------cut here---------------start------------->8--- This is a string: ~"Nil"~. --8<---------------cut here---------------end--------------->8--- The generated latex is as follows (I show just the fragment of interest): #+begin_src latex This is a string: \textasciitilde{}"Nil"\textasciitilde{}. #+end_src I see the same problem with html export. Note that syntax highlighting works correctly. Is this a bug? Thanks, Alan