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

Nesting @books? #17

Open
RandomDSdevel opened this issue Jul 31, 2017 · 3 comments
Open

Nesting @books? #17

RandomDSdevel opened this issue Jul 31, 2017 · 3 comments

Comments

@RandomDSdevel
Copy link

@zyedidia: Could you make it so that I can nest @books if I can't do so already? What I'd like to do is have a top-level @book-directive file containing the top-level table of contents, then have lit pull in any tables of contents it finds in @book-directive files linked to from this top-level one imported in to that latter one, allowing me to string together nested tables of contents. For example:

In the top-level @book-directive file:

⋮

@s Table of Contents

[Reference to another `@book` directive file relative to this one](link-target)

In the referenced @book-directive file:

⋮

@s Table of Contents

[Reference to another `@book` directive file relative to this one](link-target)

Desired result in top-level @book-directive file:

⋮

# Table of Contents

<!--Top-level ToC entry-->
  <!--Next-level ToC entry pulled in from secondary file-->

Basically, I want to be able to string tables of contents together like that. This might be related to #7, methinks? It might be useful to do something similar with ToCs outside of @book-directive files if those ever exist.

@RandomDSdevel
Copy link
Author

In the meantime, perhaps I should just go learn LaTeX…

@zyedidia
Copy link
Owner

zyedidia commented Aug 3, 2017

I'm sorry but it's unlikely I'll be able to implement something like this mostly because it has been a few years since I actively worked on this project and I don't have very much time at the moment.

@RandomDSdevel
Copy link
Author

RandomDSdevel commented Aug 3, 2017

That's fine; I can use something else like LaTeX or one of the other Markdown literate-programming document systems available here on GitHub. Good luck with your other project(s.) I'll let you decide whether to leave this issue open for future reference or just to close it.

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

2 participants