emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: "runaway argument" exporting: * _is_?
Date: Fri, 26 Apr 2013 15:37:16 +0200	[thread overview]
Message-ID: <86y5c5za43.fsf@somewhere.org> (raw)
In-Reply-To: 878v458pt8.fsf@gmail.com

Hi Nicolas,

Nicolas Goaziou wrote:
> Greg Minshall <minshall-63aXycvo3TyHXe+LvDLADg@public.gmane.org> writes:
>> * _is_?
>> exporting via "C-c C-e lO" (or, "lo"), i get an error from latex.
>> if i change H:2 to H:1, all (seemingly) works.  here is a diff of the
>> .tex file generated by each H:
>>> \section[\underline{is}?]{\underline{is}?}
>>> \label{sec-1}
>> am i doing something wrong?  (this is fallout converting from 7.9.3f to
>> 8.)
> Isn't it a LaTeX limitation? What would the correct LaTeX code be in that
> case?

I have exactly similar problems with fboxes used for framing the tags (see
function `org-latex-format-headline-default-function'): I use the following
code for having nicer boxes around the tags:

  (format "\\hfill{}\\fbox{\\textsc{%s}}"

When such a code (\fbox) is put between the [], everything breaks... LaTeX

AFAICS, there are 2 ways to solve this:

- not using the [] notation when the "short title" is exactly the same as the
  "long title"

- having an heuristic to clean the "long title" for converting it into a
  "short" one (like remove all LaTeX macros, keep text only -- not sure it's
  good, because the tags would be "glued" next to the title)

I guess the first point would make more sense. What do you think?

Best regards,

Sebastien Vauban

  reply	other threads:[~2013-04-26 13:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25 22:00 "runaway argument" exporting: * _is_? Greg Minshall
2013-04-26 12:00 ` Nicolas Goaziou
2013-04-26 13:37   ` Sebastien Vauban [this message]
2013-04-29 15:07   ` Greg Minshall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86y5c5za43.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).