From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Eduardo Mercovich <eduardo@mercovich.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org is exporting to tex an asterisk between "section" and "{"
Date: Sat, 5 Mar 2016 10:10:21 +0000 [thread overview]
Message-ID: <877fhh6xrm.fsf@ucl.ac.uk> (raw)
In-Reply-To: 871t7qvsrm.fsf@mercovich.net
On Friday, 4 Mar 2016 at 18:26, Eduardo Mercovich wrote:
> Hi 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.
> Thank you! :)
>
> 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]],
,----
| ‘num:’
| Toggle section-numbers (‘org-export-with-section-numbers’). It can
| also be set to a number ‘n’, so only headlines at that level or
| above will be numbered. Finally, irrespective of the level of a
| specific headline, the numbering of it can be disabled by setting
| the ‘UNNUMBERED’ property to non-‘nil’. This also affects
| subheadings.
`----
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.
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.91.1, Org release_8.3.4-626-gb62d55
next prev parent reply other threads:[~2016-03-05 10:10 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 [this message]
2016-03-08 12:30 ` Eduardo Mercovich
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
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=877fhh6xrm.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=eduardo@mercovich.net \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).