From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: new(ish) behaviour wrt to {s & }s
Date: Sun, 02 Feb 2014 08:55:16 +0100
Message-ID: <87zjmaosnv.fsf@gmail.com>
References: <871tzmmh3h.fsf@jnanam.net>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45263)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1W9rtN-0006X8-Uj
	for emacs-orgmode@gnu.org; Sun, 02 Feb 2014 02:55:07 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1W9rtI-0006ke-5E
	for emacs-orgmode@gnu.org; Sun, 02 Feb 2014 02:55:01 -0500
Received: from mail-wg0-x22e.google.com ([2a00:1450:400c:c00::22e]:39945)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1W9rtH-0006kY-UE
	for emacs-orgmode@gnu.org; Sun, 02 Feb 2014 02:54:56 -0500
Received: by mail-wg0-f46.google.com with SMTP id x12so10544074wgg.25
	for <emacs-orgmode@gnu.org>; Sat, 01 Feb 2014 23:54:54 -0800 (PST)
In-Reply-To: <871tzmmh3h.fsf@jnanam.net> (Benjamin Slade's message of "Sat, 01
	Feb 2014 18:35:46 -0700")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: Benjamin Slade <slade@jnanam.net>
Cc: emacs-orgmode@gnu.org

Hello,

Benjamin Slade <slade@jnanam.net> writes:

> At some point orgmode has started escaping {s and }s which I don't want
> to be escaped on conversion to LaTeX. For example when I put in orgmode
> \textsubscript{some subscript}, I get out in the .tex file
> \textsubscript\{some subsubscript}. Likewise with a user-defined
> function like \Bracketed{...}.

Org doesn't support full LaTeX syntax. If you want to insert raw LaTeX,
you need to use specific markup, for example an export snippet:

  @@latex:\textsubscript{some subsubscript}@@

> Is there a flag/option I can use to tell orgmode to *never* escape my {s
> and }s on export to LaTeX?

No. But you could write a filter to do so, see:

  (info "(org) Advanced configuration").


Regards,

-- 
Nicolas Goaziou