ddfreyne changed the topic of #nanoc to: 3.8.0 (May 4th) - 4.0.0b2 (May 23rd) | web http://nanoc.ws/ | repo http://bit.ly/XE6e3G | issues http://bit.ly/VfXaSV | forum http://ho.io/n-discuss | irclog http://irclog.whitequark.org/nanoc
pkunc has joined #nanoc
pkunc1 has joined #nanoc
<guardian> ddfreyne: I ended up doing this in my own copy of the kramdown filter
<guardian> if params[:auto_close_img_and_br]
<guardian> content = content.gsub(/<((img|br)[^>]*)>/, '<\1/>')
<guardian> end
<guardian> is this interesting as a PR?
pkunc has quit [Ping timeout: 265 seconds]
dbr_vince has joined #nanoc
siwica has joined #nanoc
siwica has quit [Quit: ERC Version 5.3 (IRC client for Emacs)]
VitamineD has quit [Quit: mi dormas]
VitamineD has joined #nanoc
VitamineD has quit [Remote host closed the connection]
jugglinmike has joined #nanoc
cDlm has joined #nanoc
siwica has joined #nanoc
<siwica> Is it possible to specify the output directory as a parameter when compiling with 'nanoc compile' or can it only be specified in nanoc.yaml?
<guardian> you can try to hack it around with an env variable, then in the preprocess block you assign @config[:output_dir] = ENV['NANOC_OUTPUT']
<guardian> and then you do $ NANOC_OUTPUT=xxx bundle exec nanoc compile
<siwica> guardian: ok, where exactly do I specify the preprocess blog? (first day using nanoc...)
<siwica> *block
<guardian> in Rules file
<siwica> ok, I see
<siwica> thanks!
<guardian> you're welcome
<siwica> ok, it worked. Still not elegant, but whatever ;)
siwica has quit [Ping timeout: 265 seconds]
cDlm has quit [Remote host closed the connection]
VitamineD has joined #nanoc
VitamineD has quit [Ping timeout: 256 seconds]
vy has joined #nanoc
<vy> ddfreyne: In Rules, I move binary files (e.g., 20150609-foo#bar.pdf) to /2015/06/09/foo/bar.pdf, which works fine. (See https://github.com/vy/vy.github.io/blob/source/Rules) But when I have two binary files with different extensions (e.g., 20150609-foo#bar.pdf and 20150609-foo#bar.odp) nanoc complains that: Found 2 content files for 20150609-foo#bar; expected 0 or 1. Any ideas?
vy has quit [Ping timeout: 246 seconds]
<guardian> ddfreyne: I'm using colorize syntax filter + rouge
<guardian> ddfreyne: is there an easy way to detect language to be highlighted?
<ddfreyne> guardian: Your modification of the kramdown filter is useful, I think, although I’d rather have it run through Nokogiri. (XML/XHTML is notoriously hard to parse)
<number-six> ddfreyne: I'll pass that on when I see vy here.
<ddfreyne> guardian: not sure what you mean wrt colorize_syntax and rouge. The colorize_syntax filter already has some logic for extracting the language.
VitamineD has joined #nanoc