+[2017-07-07T17:49:21Z]jobotI found this. It seems to work: http://hadihariri.com/2013/12/24/migrating-from-wordpress-to-jekyll/ +[2017-07-07T17:49:21Z]jobotRequired this: https://stackoverflow.com/questions/39222534/failed-to-build-native-extension and a few gem dependencies +[2017-07-07T17:49:22Z]jekyllrbTitle: Migrating from WordPress.com to Jekyll – Hadi Hariri (at hadihariri.com) +[2017-07-07T17:49:23Z]jekyllrbTitle: ruby on rails - Failed to build native extension - Stack Overflow (at stackoverflow.com) +[2017-07-07T18:54:02Z]ramseyI've been doing some searching for an issue I'm seeing with Jekyll and GFM, but all that's coming up are issue about fenced code blocks. My issue is with using inline backticks (i.e. `code here`). Jekyll appears to be filtering that through the syntax-highlighter and is generating table output, due to my use of "line_numers: true" in _config.yml. Has anyone else noticed this?
If I remove "line_numbers: true", then everything works as expected, but I don't see line numbers in my fenced code blocks
+[2017-07-07T19:09:19Z]ramseyah ha! I was doing "kramdown: syntax_highlighter_opts: line_numbers: true" in _config.yml, which add line numbers to all code (even inline code). If I change it to "kramdown: syntax_highlighter_opts: block: line_numbers: true", (note "block") it works as expected. +[2017-07-07T19:09:31Z]ramseyLine numbers appear on fenced code blocks, but do no appear on inline code. +[2017-07-25T23:30:16Z]jaybe./fs debug +[2017-07-25T23:30:16Z]jekyllrbNo keys matched that query. +[2017-07-25T23:30:30Z]jaybeelmiko, there is --verbose to begin with