Would there be interest in creating a Grunt task that would run Biggie each time a target markdown file is changed?

This is probably upstream in big

Need a freerange gatekeeper server for this

I tried putting a block of code on a slide using ``` and it and became a tiny unreadble mess.

• Rebuild in a real framework
• Make image embedding simple
• UI for everything
• Redesign completely

Seeing awful issues around iframes and location access

npm install -g biggie is throwing:

npm ERR! fetch failed https://github.com/tmcw/CodeMirror/archive/module-export.tar.gz
npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404

Indeed, that package doesn't exist. Installing from source works fine in the meantime.

I've been using this as a great command-line tool and writing presos in markdown. Any possibility that biggie could consume big as a dependency to avoid the disconnect between this and your awesome updates?

I like to put links on my presentations, but any interaction that I do on the page makes it goes to the next slide. Left clicking goes to the next slide followed soon by the page load of the link, feels weird. Right click (to open to a new tab) just goes to the next slide.

Is this only me?

I didn't dive into the source... how hard would be to allow (right) clicking on links?

This image link in https://github.com/tmcw/biggie/blob/gh-pages/index.html#L45 is broken:

http://farm3.staticflickr.com/2608/3801835477_b87502a888.jpg

I think the Flickr original may have been deleted: http://flickr.com/photo.gne?id=3801835477