octopress / codefence

Write beautiful fenced code snippets with in any template.
MIT License
16 stars 16 forks source link

Options for linenos and start are ignored and result in no highlighting #15

Open detly opened 8 years ago

detly commented 8 years ago

Using the triple backticks with options linenos:true and start:5 result in no highlighting and verbatim rendering of those options in the code.

Here's the codefence part of the source:

```c
const int magic;
const int not_magic;

Here's a screenshot:

![octopress cf bug](https://cloud.githubusercontent.com/assets/311239/13207365/c70c5000-d961-11e5-907a-7771e3cea64d.png)

To reproduce:

First, write a Gemfile containing:

source 'https://rubygems.org'

gem 'octopress', '~> 3.0'


Then run `bundle` (I did this under an RVM managed Ruby 2.3.0).

Then do `mkdir src` and run `octopress new src`.

Then do

cd src jekyll serve


The results of this are at https://github.com/detly/octopress-test

I'm doing this on Ubuntu 14.04.1 with an RVM installed Ruby 2.3.0. Gems installed (purely from the `bundle` command) are:

Using colorator 0.1 Using ffi 1.9.10 Using sass 3.4.21 Using rb-fsevent 0.9.7 Using kramdown 1.9.0 Using liquid 3.0.6 Using mercenary 0.3.5 Using rouge 1.10.1 Using safe_yaml 1.0.4 Using redcarpet 3.3.4 Using titlecase 0.1.1 Using bundler 1.11.2 Using octopress-deploy 1.3.0 Using rb-inotify 0.9.7 Using jekyll-sass-converter 1.4.0 Using listen 3.0.6 Using jekyll-watch 1.3.1 Using jekyll 3.1.2 Using octopress-escape-code 2.1.1 Using octopress-hooks 2.6.1 Using octopress-code-highlighter 4.3.0 Using octopress 3.0.11 Using octopress-codefence 1.7.0

detly commented 8 years ago

It looks like this might be related to my other installation woes. I'm not really sure where I've gone wrong, but perhaps I'm using the wrong version of Jekyll.