From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [bug] Partially disable interpretation of subscripts Date: Fri, 20 Dec 2013 21:53:34 +0100 Message-ID: <87y53fjlbl.fsf@gmail.com> References: <86sitntsvh.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43863) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vu74m-00072f-N6 for emacs-orgmode@gnu.org; Fri, 20 Dec 2013 15:53:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vu74c-000631-L5 for emacs-orgmode@gnu.org; Fri, 20 Dec 2013 15:53:40 -0500 Received: from plane.gmane.org ([80.91.229.3]:34252) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vu74c-00062r-En for emacs-orgmode@gnu.org; Fri, 20 Dec 2013 15:53:30 -0500 Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Vu74a-0005xN-Sj for emacs-orgmode@gnu.org; Fri, 20 Dec 2013 21:53:28 +0100 In-Reply-To: <86sitntsvh.fsf@somewhere.org> (Sebastien Vauban's message of "Fri, 20 Dec 2013 17:00:18 +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: Sebastien Vauban Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org Hello, "Sebastien Vauban" writes: > In order to be able to write names such as CODE_STATUT without STATUT > being written in subscript, I'm using the {} value for the ^ option. > > #+TITLE: ECM Subscript > #+OPTIONS: ^:{} > > * Underscores in text > > x_i + x^2 + x^{2} + x_{i} > > | Key | Value | > |----------------------+-------| > | CODE_STATUT | 1 | > | CONTRAT\_DEBUT\_DATE | 2 | > | CONTRAT_FIN_DATE | 3 | > > Though, doing so, > > - a_b is interpreted as subscript > - a_{b} is left as is > > In a way, the opposite of what I'm expecting. > > Am I missing something? No, I forgot a `not' in a recent patch. This should now be fixed. Thank you for reporting it. Regards, -- Nicolas Goaziou