From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Randby Subject: Re: Multiple underscores crash org latex export; other exporters survive Date: Sat, 3 Dec 2016 23:53:38 -0500 Message-ID: <50e77033-c13c-c0be-5d4a-ec5c107e93ae@gmail.com> References: <49b70a0c-f81b-660b-e2f5-9921ab488d65@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58556) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cDOo9-0006To-Sx for emacs-orgmode@gnu.org; Sat, 03 Dec 2016 23:53:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cDOo9-0003Dh-4G for emacs-orgmode@gnu.org; Sat, 03 Dec 2016 23:53:49 -0500 Received: from mail-io0-x22f.google.com ([2607:f8b0:4001:c06::22f]:34425) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cDOo8-0003DO-TK for emacs-orgmode@gnu.org; Sat, 03 Dec 2016 23:53:49 -0500 Received: by mail-io0-x22f.google.com with SMTP id c21so503186409ioj.1 for ; Sat, 03 Dec 2016 20:53:48 -0800 (PST) In-Reply-To: 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" To: "Charles C. Berry" Cc: emacs-orgmode@gnu.org On 12/03/2016 05:31 PM, Charles C. Berry wrote: > On Sat, 3 Dec 2016, Scott Randby wrote: > >> On 12/03/2016 02:40 PM, Scott Otterson wrote: >>> When an org file contains a string with more than one underscore, the >>> orgmode export result will crash latex (example attached). On the >>> other hand, the org html export does finish successfully, and while >>> result is odd, it's odd in a way that makes the problem visible and easy >>> to identify. >> >> I exported your file using LaTeX export without trouble. The result does >> look odd, but that is because the string you gave is missing the braces >> needed to make it export properly. The output messages warn that the >> string contains a double subscript, so the problem is with the string >> and not Org's LaTeX export. >> >> Your string: a_variable_deleteThisAndItWorks >> >> Properly formed string: a_{variable_{deleteThisAndItWorks}} > > I don't think the OP wanted double subscripts. If the OP really wanted > "heavily underscored code snippets", something like: > > Code snippet: ~a_variable_deleteThisAndItWorks~ > > seems like the way to go. It seems I misunderstood the original question. There is an interesting issue here. I sometimes want to use ~ in a code snippet, so I can't use ~code snippet~. Yet, Org code: \verb@a_variable_deleteThisAndItWorks@ Exported LaTeX: \verb@a\(_{\text{variable}}_{\text{deleteThisAndItWorks}}\)@ The exported LaTeX is not what we want. Instead, Org code: #+latex:\verb@a_variable_deleteThisAndItWorks@ Alternative: @@latex:\verb@a_variable_deleteThisAndItWorks@@@ Exported LaTeX: \verb@a_variable_deleteThisAndItWorks@ I've wondered why \verb isn't exported correctly without specifying it as literal LaTeX, but I don't have the expertise to be able to determine why. Scott