Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for table of contents #17

Open
mrvdb opened this issue Jun 13, 2014 · 5 comments
Open

Add support for table of contents #17

mrvdb opened this issue Jun 13, 2014 · 5 comments

Comments

@mrvdb
Copy link

mrvdb commented Jun 13, 2014

I'm using some org documents in a blog for publishing. Converting them with org-ruby to html works excellent, except for the table of contents.

Taking the 'toc' setting from #+OPTIONS in the org-file would be great.

@snosov1
Copy link

snosov1 commented Oct 1, 2014

I don't know whether it will be applicable, but you can use the org-toc package as a workaround. In short, you simply add a :TOC: tag to a headline, and it gets updated with the current table of contents upon saving.

You can also define your own function for turning headings into hrefs. Like, if you add a :TOC@1@myfunc: tag, then it will try to use org-toc-hrefify-myfunc to turn heading into a href. Github and org href styles are supported out-of-the-box.

@mrvdb
Copy link
Author

mrvdb commented Oct 2, 2014

Excellent suggestion, thanks! For some of the documents this is indeed a viable workaround.

@larstvei
Copy link

larstvei commented Apr 7, 2015

Hi!

I also miss this feature, and would prefer to avoid a workaround. If someone would point me in the right direction in adding this feature I would love to give implementing it a shot!

@ewa
Copy link

ewa commented Jan 21, 2016

Another +1 here. This would be really good to have. I love that GitHub (using org-ruby) renders Org files nicely, but I wish tables of contents came through!

@angrybacon
Copy link

Likewise, toc-org is not a viable option to me because I would still have the TOC in my files (takes a lot of space). Not only could it parse #+OPTIONS but it could also support #+TOC. Here is what I tried:

* Heading 1

#+TOC: headlines 1 local

** Subheading 1
** Subheading 2
** Subheading 3

* Heading 2

#+TOC: headlines 1 local

** Subheading 1
** Subheading 2

Here is the documentation I referred to: http://orgmode.org/manual/Table-of-contents.html.

Also, is the project still maintained? I see the last commit is from early 2015.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants