From mboxrd@z Thu Jan  1 00:00:00 1970
From: James Harkins <jamshark70@gmail.com>
Subject: LaTeX export: {} on separate lines are escaped, why?
Date: Sat, 27 Jul 2013 09:41:05 -0400
Message-ID: <87li4s2k9a.wl%jamshark70@dewdrop-world.net>
Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:33379)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jamshark70@gmail.com>) id 1V34k9-0000GZ-FT
	for emacs-orgmode@gnu.org; Sat, 27 Jul 2013 09:41:10 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jamshark70@gmail.com>) id 1V34k8-00020I-M7
	for emacs-orgmode@gnu.org; Sat, 27 Jul 2013 09:41:09 -0400
Received: from mail-ye0-x22e.google.com ([2607:f8b0:4002:c04::22e]:45412)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jamshark70@gmail.com>) id 1V34k8-0001zK-IC
	for emacs-orgmode@gnu.org; Sat, 27 Jul 2013 09:41:08 -0400
Received: by mail-ye0-f174.google.com with SMTP id q9so899695yen.19
	for <emacs-orgmode@gnu.org>; Sat, 27 Jul 2013 06:41:07 -0700 (PDT)
Received: from dlm-A6200.gmail.com (cpe-98-157-146-44.ma.res.rr.com.
	[98.157.146.44])
	by mx.google.com with ESMTPSA id a62sm70788359yhk.4.2013.07.27.06.41.06
	for <emacs-orgmode@gnu.org>
	(version=TLSv1.2 cipher=RC4-SHA bits=128/128);
	Sat, 27 Jul 2013 06:41:07 -0700 (PDT)
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: orgmode <emacs-orgmode@gnu.org>

Just wondering if there's a better way to handle LaTeX commands written inline, when the command arguments span a line break. Currently, LaTeX export preserves curly braces as is if a pair of them is on a single line, but it escapes them if there's a line break in between:

~~ org
Sections may be created as subpatches, using \inpcode{[route go
stop]} to start or stop the section, as in the very simple example in
Figure \ref{pd_comp}a.
~~

~~ Exported LaTeX:
Sections may be created as subpatches, using \codeident\{[route go
stop]\} to start or stop the section, as in the very simple example in
Figure \ref{pd_comp}a.
~~

(\codeident is a custom command I defined in the preamble, as semantic markup for \texttt.)

In the PDF, \ref{pd_comp} turns into a figure number, as I would expect, but \codeident\{...\} sets the enclosed string in the normal font rather than fixed-width (with visible {}, which shouldn't be in the printed output).

I do have a workaround:

~~ org
Sections may be created as subpatches, using
#+LaTeX: \inpcode{[route go stop]}
to start or stop the section, as in the very simple example in
Figure \ref{pd_comp}a.
~~

... where "#+LaTeX:" prevents M-q from breaking the braces onto separate lines, but -- this has tripped me up a few dozen times working on this article, so I thought it would be worth asking if this is really the ideal behavior.

hjh