Alexandre ZANNI
Alexandre ZANNI
And of course I'll have a feature request to support JSON input too.
@likeadoc It has been published: https://open-vsx.org/extension/shd101wyy/markdown-preview-enhanced @shd101wyy Could you claim the namespace to avoid the warning?  Here's how to: https://github.com/eclipse/openvsx/wiki/Namespace-Access
Adding the following to my `_config.yml` doesn't change anything: ``` marked: smartypants: false ``` In both case the render is ```html || a b ` ` pipe pipe ```
@dpfranklin : Thanks, I was not sure if it was due to Marked or only hexo-renderer-marked.
Marked seems no so much updated recently (https://github.com/chjj/marked/issues/724). And Marked is not [CommonMark](http://commonmark.org/) compliant (https://github.com/chjj/marked/issues/563). It's maybe time to switch (as official) to [commonmark.js](https://github.com/jgm/commonmark.js), [markdown-it](https://github.com/markdown-it/markdown-it) or [remarkable](https://github.com/jonschlinkert/remarkable). There are already...
I tried [hexo-renderer-markdown-it](https://github.com/celsomiranda/hexo-renderer-markdown-it) and the both cases works well now (with default which is GMF support) : ``` `|` \| ``` 
Maybe Hexo team should think about considering to use markdown-it renderer as default and official renderer, because Marked seems to begin to die (https://github.com/chjj/marked/issues/724).
1) Using PySide for Qt bindings is a bad idea because it's officially a [dead](https://pyqt.developpez.com/actu/80721/Le-projet-PySide-est-declare-abandonne-en-2015-il-ne-reste-plus-que-PyQt-comme-binding-Python-de-Qt/) project. Use [PyQt](https://riverbankcomputing.com/software/pyqt/intro) instead. 2) Using PySide for Qt bindings is a bad idea because...
Added to the README : https://github.com/IceCTF/ColdCore/pull/23
But now: ``` ./ctftool challenges add problem.yml Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/peewee.py", line 3768, in execute_sql cursor.execute(sql, params or ()) sqlite3.IntegrityError: NOT NULL constraint failed: challenge.flag During handling...