From: Eduardo Mercovich <eduardo@mercovich.net>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org is exporting to tex an asterisk between "section" and "{"
Date: Tue, 08 Mar 2016 09:30:17 -0300 [thread overview]
Message-ID: <87si015ezq.fsf@mercovich.net> (raw)
In-Reply-To: <877fhh6xrm.fsf@ucl.ac.uk>
Dear Eric.
>>>> Troubleshooting a lack of ToC content in a exported PDF from org, I
>>>> found this issue. [...]
>>> Make sure you have
>>> #+options: num:t
>>> set. Otherwise, sections are unnumbered. I'm not sure what the default
>>> is. Maybe you have "num:nil"?
>> I had nothing in the document, and your suggestion did the trick. [...]
>> However, I can't find this in the documentation... shouldn't something
>> like this be the default? If not, the ToC and the links are not rendered
>> or non-functional.
> It is documented, in [[info:org#Export%20settings][info:org#Export
> settings]], [...]
> Easy to miss as it is not LaTeX specific, of course. It's a general
> setting that affects potentially any export engine but is obviously only
> relevant to some.
Sorry, I was totally unclear...
Being a total newbie I can't say that the resulting syntax is incorrect
(is it?), but at least in the case of latex, *not expressing this
specific option creates a non-functional latex file*.
Shouldn't the exporter take care of this? Or at least, never export the
asterisk between the "section" and the brace (just in case, "{" since
I'm not an English native speaker).
Sorry if the case is irrelevant, I tried reading before posting but
found nothing to reassure me.
Thanks... :)
--
eduardo mercovich
Donde se cruzan tus talentos
con las necesidades del mundo,
ahí está tu vocación.
next prev parent reply other threads:[~2016-03-08 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 19:15 Org is exporting to tex an asterisk between "section" and "{" Eduardo Mercovich
2016-03-04 19:45 ` Eric S Fraga
2016-03-04 21:26 ` Eduardo Mercovich
2016-03-05 10:10 ` Eric S Fraga
2016-03-08 12:30 ` Eduardo Mercovich [this message]
2016-03-10 8:56 ` Eric S Fraga
2016-03-15 16:07 ` Eduardo Mercovich
2016-03-15 17:11 ` Eric S Fraga
2016-03-10 9:57 ` Nicolas Goaziou
2016-03-15 16:02 ` Eduardo Mercovich
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87si015ezq.fsf@mercovich.net \
--to=eduardo@mercovich.net \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.