-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Hexo 3.2.0-beta.2 test result report #1627
Comments
set and test results are as below:
after(3.2.0-beta.2):
This is the cold start time, as the cache added, hot start will be quicker. |
I think we should recommend setting highlight.js's auto detect to false in the document. |
Yes, It used to save a lot time for don't need to choose language, but at this time, it looks like just resulting more and more problems. |
It's disabled by default in Hexo 3.2. |
@tommy351 do you mean disabling the config? |
hexo-starter is not updated yet. But it has been disabled in hexo core. |
But the default config will be overwritten by config value, isn't it? |
I think we can remove the auto-detect option from _config.yml, and educate people form the rule that add specific language for codeblocks. |
@Xuanwo I second the idea. We can override the value and state in documentation that it will be hardcoded. Actually we could also set |
refs Hexo 3.2.0-beta.2 test result report · Issue #1627 · hexojs/hexo hexojs/hexo#1627
Track in #1786 |
I meet this problem too. I have been troubled for a whole day. Thanks very much. It's working!! |
set auto_detect to false solved my problem. |
1 similar comment
set auto_detect to false solved my problem. |
met this prob, thank you! |
i met this issue too.And my problem was due to that i didn't specify language for the code in markdown.so,you should specify your code language.May it can help you. |
I have solved the problem by changing auto_detect to false too~ |
ref: https://travis-ci.org/Xuanwo/xuanwo.github.io/builds/95182069
I meet a
TypeError: Cannot set property 'lastIndex' of undefined
error, and error message as below@tommy351
The text was updated successfully, but these errors were encountered: