From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Escape individual underscore? Date: Tue, 03 Mar 2015 15:53:34 -0500 Message-ID: <87lhjddcq9.fsf@alphaville.usersys.redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59711) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YStp9-00024R-Bg for emacs-orgmode@gnu.org; Tue, 03 Mar 2015 15:53:52 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YStp6-0003b8-33 for emacs-orgmode@gnu.org; Tue, 03 Mar 2015 15:53:51 -0500 Received: from plane.gmane.org ([80.91.229.3]:60549) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YStp5-0003ax-SG for emacs-orgmode@gnu.org; Tue, 03 Mar 2015 15:53:48 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1YStp0-0007kr-Ac for emacs-orgmode@gnu.org; Tue, 03 Mar 2015 21:53:42 +0100 Received: from nat-pool-bos-t.redhat.com ([66.187.233.206]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Mar 2015 21:53:42 +0100 Received: from ndokos by nat-pool-bos-t.redhat.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Mar 2015 21:53:42 +0100 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@gnu.org Jacob Gerlach writes: > Hi List, > > I want to include a literal underscore in LaTeX export, like FOO_BAR. Right now I get: > FOO$_{\text{BAR}}$ > > Contrary to this stackexchange question, if I try to escape the underscore with a backslash, I get: > FOO$\backslash$$_{\text{BAR}} > > I've found that I can setĀ org-export-with-sub-superscripts to "{}" to avoid this problem, but I'd rather escape individual > underscores on a case by case basis. Is this possible? > I don't think so. FWIW, I always set #+OPTIONS: ^:{} in my files. That allows me to use a_b for the majority of my use cases, but still allows {subscripts} in the rare cases when I need them. I'm not sure how useful it would be but maybe there should be a setting to accommodate the inverse case: mostly subscripts a_b but allow literal underscores using some additional markup. Nick