Repository navigation
Nested/Recursive includes #2643
Description
Activity
Hi @phil-flip , docsify doesn't provide the
LaTeXconversion originally. Are you using a plugin for LaTeX to markdown?- addedwait for informationsomething is not clear, waiting for the author of the issue/prsomething is not clear, waiting for the author of the issue/pr
on Dec 6, 2025 I used pandoc with a custom sed-command. But that's not important for this feature request. The Problem is that I can't have includes recursivly, which should be possible as I wrote a cursed Docsify plugin for it, but would be better in the backend.
I used pandoc with a custom sed-command. But that's not important for this feature request. The Problem is that I can't have includes recursivly, which should be possible as I wrote a cursed Docsify plugin for it, but would be better in the backend.
Sorry, I don't fully get it. As I mentioned, docsify doesn't support the
LaTeXconversion, nor parse any LaTeX syntax by itself. Are you using any docsify plugin that supportingLaTeXin your project?Forget LaTeX. It's not about it.
I only want to have recursive embeds of other markdown files, which is supported by Docsify.. Currently, this only goes one level deep. So when there is another embed inside that file, it will not work.Forget LaTeX. It's not about it. I only want to have recursive embeds of other markdown files, which is supported by Docsify.. Currently, this only goes one level deep. So when there is another embed inside that file, it will not work.
Gotcha, we will evaluate this feature and to see if it could be introduce into docsify.
- removedwait for informationsomething is not clear, waiting for the author of the issue/prsomething is not clear, waiting for the author of the issue/pr
on Dec 9, 2025
Problem or Desire
For our new docs at work, we want to convert LaTeX to Markdown. The problem is that it has quite a lot of nested documents with
\include, which Docsify can only go one level deep.Proposal
Docsify should resolve the included markdown files recursively. With protection against looping embeds.
Additional Context
There is no need to make it a setting to preserve backwards compatibility.
First time