From: Scott Randby <srandby@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>,
Carsten Dominik <dominik@uva.nl>,
Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: setting local variables
Date: Thu, 21 Sep 2017 09:00:19 -0400 [thread overview]
Message-ID: <54f1946b-8c4d-7acf-b55f-8fbcd4aaff5b@gmail.com> (raw)
In-Reply-To: <CAFyQvY0D1BR9CA+_vonS+u6QCuikJ-rF+GE4WjEwKFhHqSSNhA@mail.gmail.com>
On 09/20/2017 07:16 PM, Kaushal Modi wrote:
> I have to agree with Carsten. I use unnumbered table of contents all the
>> time in web pages. Almost all of my Org files that generate web pages have
>> the following:
>>
>> #+options: num:nil toc:t
>>
>
> @Scott Please see that other thread[1]. I have this exact use case. And if
> the case 3 discussed in that thread is supported all should be good.
>
> [1]: http://lists.gnu.org/archive/html/emacs-orgmode/2017-09/msg00497.html
>
Okay, I don't really understand the issue being discussed in the thread, but if num:nil gives me an unnumbered table of contents after HTML export, I'm good. I also export to LaTeX, but I recognize that there are issues with LaTeX table of contents and I just work around them.
I need to sit down and read the Org manual. For years, I've been using toc:t and getting more in the table of contents than I wanted. Discovering that I can use something like toc:1 was exactly what I needed a long time ago. I know there are other things in Org that I want now and just don't know about. There are disadvantages to my haphazard approach to Org.
Scott
next prev parent reply other threads:[~2017-09-21 13:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 21:53 setting local variables Eric Abrahamsen
2017-08-02 22:10 ` Kaushal Modi
2017-08-02 22:15 ` Eric Abrahamsen
2017-08-03 10:52 ` Nicolas Goaziou
2017-08-03 16:11 ` Eric Abrahamsen
2017-08-03 22:02 ` Nicolas Goaziou
2017-08-03 22:49 ` Eric Abrahamsen
2017-08-04 0:42 ` Eric Abrahamsen
2017-08-04 15:37 ` Nicolas Goaziou
2017-08-05 1:06 ` Eric Abrahamsen
2017-08-05 8:50 ` Nicolas Goaziou
2017-08-05 19:14 ` Eric Abrahamsen
2017-09-05 11:48 ` Rasmus
2017-09-05 16:57 ` Eric Abrahamsen
2017-09-06 8:56 ` Rasmus
2017-09-06 10:38 ` Nicolas Goaziou
2017-09-06 12:42 ` Rasmus
2017-09-06 13:08 ` Nicolas Goaziou
2017-09-06 16:33 ` Eric Abrahamsen
2017-09-06 16:57 ` Nicolas Goaziou
2017-09-06 17:44 ` Eric Abrahamsen
2017-09-07 8:56 ` Rasmus
2017-09-07 12:48 ` Nicolas Goaziou
2017-09-07 15:01 ` Eric Abrahamsen
2017-09-10 13:55 ` Nicolas Goaziou
2017-09-20 16:17 ` Carsten Dominik
2017-09-20 18:42 ` Scott Randby
2017-09-20 23:16 ` Kaushal Modi
2017-09-21 8:38 ` Carsten Dominik
2017-09-21 9:39 ` Rasmus
2017-09-21 9:58 ` Carsten Dominik
2017-09-21 19:21 ` Nicolas Goaziou
2017-09-21 21:25 ` Kaushal Modi
2017-09-22 7:22 ` Carsten Dominik
2017-09-22 9:09 ` Rasmus
2017-09-21 13:00 ` Scott Randby [this message]
2017-09-21 7:45 ` Eric S Fraga
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=54f1946b-8c4d-7acf-b55f-8fbcd4aaff5b@gmail.com \
--to=srandby@gmail.com \
--cc=dominik@uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=kaushal.modi@gmail.com \
/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).