Closed kaedea closed 9 years ago
Could you add source code of the article, hexo version and hexo-renderer-marked version please?
C:\Users\estel>hexo version hexo-cli: 0.1.7 os: Windows_NT 6.3.9600 win32 x64 http_parser: 2.3 node: 0.12.2 v8: 3.28.73 uv: 1.4.2-node1 zlib: 1.2.8 modules: 14 openssl: 1.0.1m
Genymotion是一款顺畅和容易(fast and easy-to-use)使用的Android模拟器,可以用来运行和调试你的APP。Genymotion 来自于AndroVM 这个开源项目,基于 x86 和 VirtualBox,支持 OpenGL 加速,可以用于 Mac/Win/Linux
。最近发布了新版,支持了 Android2.3/4.3,新增了拖拽安装 apk,移除了 Google 市场(后面提供解决方案)。另外增加了功能更丰富的付费版,个人可以继续使用免费版。
It looks that the # singal does not work here in comment either. Do I use it in a wrong way?
go in your package.json
file and get hexo version and hexo-renderer-marked please. I test your code, and it works fine with hexo : 3.1.1 and hexo-renderer-marked : 0.2.5
Thanks!
Got same problem. hexo 3.1.1 and hexo-renderer-marked 0.2.5.
\ - ``` all work fine, only # singal doesn't work
@jin5354 copy your source code please
@LouisBarranqueiro I found the reason. There should be a space between '#' and letters.
"###word" can't work. "### word"works. Is this space absolutely necessary? I'm migrating hexo from 2.x to 3. The old hexo can correctly recognize '###word'.
Thanks for your attention. Awesome theme!
@jin5354 not absolutely, some parser can render it, but with space is the correct markdown syntax. see Daring Fireball: Markdown Syntax Documentation or Mastering Markdown · GitHub Guides.
Do you know how to upgrade the hexo-renderer-marked
dependency version in HEXO? Mine is 0.2.4
@kaedea Just run npm i hexo-renderer-marked@0.2.5
I seems that the new hexo-renderer-marked required a between #
and the title. As @h404bi said the correct markdown syntax require a space.
Thanks for your help.