-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Cannot render headings with ids? #40
Comments
Thanks. It works! |
Is this merged into the project? I had the same issues and this works for me to add |
Hi, I wonder what else do you need to do after adding this line? I still have the problem after doing that. Thanks |
I think that’s all I did. Maybe dependencies had updated?
…On Wed, 13 Dec 2017 at 11:48 Henry Zhao ***@***.***> wrote:
Hi, I wonder what else do you need to do after adding this line? I still
have the problem after doing that. Thanks
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#40 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMkUdl2gPGJQE7METdOJuacYkEZUmrwrks5s_0kmgaJpZM4Ji8ez>
.
|
@HanchengZhao Maybe you can reference this issue. If it doesn't work, I cannot solve it neither. |
@pujiaxun Thanks for the comment. My issue actually has something to do with 'hexo-toc' package. For those who might have the same problem, check out YenYuHsuan/hexo-theme-beantech#11 |
hexo-renderer-markdown-it is not compatible with hexo-toc yet even if hexo-toc claims it. |
Is this issue still up to date or it can be closed ? |
@noraj So you mean it's not a bug but a kind of feature or nonsupport? Feel free to close it if you want. |
@pujiaxun hexo-renderer-markdown-it works perfectly, it's hexo-toc that is a mess. |
This renderer cannot generate ids in headings because of Markdown-it plugin not implement it.
So I tried a solution
Just use a plugin
markdown-it-named-headings
And then add one line to render it with this plugin.
Just like this.
Could I make a PR for this?
The text was updated successfully, but these errors were encountered: