emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Andreas <tjandreas@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-reveal reaveal.js toc:nil option
Date: Wed, 13 Nov 2013 23:55:13 +0100	[thread overview]
Message-ID: <CAC=rykf0h0GrrobgHkF3ma30fLrZM-DexXHkofarbXDRz23KBg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]

I did some brute force bug tracking and manage to track down the problem.

I made two different files:
test1.org:
#+TITLE:     Test 1
#+OPTIONS: toc:nil
#+INFOJS_OPT:

* Header 1
* Header 2
** Subheader 2.1

test2.org:
#+TITLE:     Test 1
#+OPTIONS: toc:nil

* Header 1
* Header 2
** Subheader 2.1

In the first example i have the header with #+INFOJS_OPT:
empty, the other file lacks this line. The first file generates a toc while
the other doesn't.

I manage to track down the variable org-html-infojs-opts-table
which has the
Value: ((path PATH "http://orgmode.org/org-info.js")
 (view VIEW "info")
 (toc TOC :with-toc)
 (ftoc FIXED_TOC "0")
 (tdepth TOC_DEPTH "max")
 (sdepth SECTION_DEPTH "max")
 (mouse MOUSE_HINT "underline")
 (buttons VIEW_BUTTONS "0")
 (ltoc LOCAL_TOC "1")
 (up LINK_UP :html-link-up)
 (home LINK_HOME :html-link-home))

It seems to me as a novice that the :with-toc is defined here and forces a
table of contents to be displayed. Not sure if this is correct but at least
it solved my problem.

The toc option is not inserted in the reveal export template and now after
testing it it looks like
#+INFOJS_OPT: toc:nil
also could have been used. The tutorial I looked at did not do it this way
so I over looked it.

regards
A

[-- Attachment #2: Type: text/html, Size: 1737 bytes --]

next             reply	other threads:[~2013-11-13 22:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 22:55 Andreas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-13 13:17 org-reveal reaveal.js toc:nil option Andreas
2013-11-13 14:23 ` Nick Dokos

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='CAC=rykf0h0GrrobgHkF3ma30fLrZM-DexXHkofarbXDRz23KBg@mail.gmail.com' \
    --to=tjandreas@gmail.com \
    --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

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).