ddfreyne changed the topic of #nanoc to: 3.6.7 (dec 9th) | 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 | gregkare smells of elderberries
gnufied has quit [Ping timeout: 252 seconds]
gnufied has joined #nanoc
pavelkunc has quit [Quit: Leaving.]
<gregkare> I've hacked together a tiny ugly script that generates a nested hash I can paste into brightbox-cli's Ruby completion script, it works with nanoc
<gregkare> I'll clean that up tomorrow, going to bed!
simplon_ has joined #nanoc
simplon has quit [Ping timeout: 250 seconds]
jarr0dsz has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ics has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
number-six has quit [Ping timeout: 252 seconds]
jaspervdj has quit [Ping timeout: 252 seconds]
alerante_ has joined #nanoc
alerante has quit [Ping timeout: 248 seconds]
ics has joined #nanoc
jugglinmike has quit [Quit: Leaving.]
francois2 has quit [Ping timeout: 272 seconds]
francois2 has joined #nanoc
<bobthecow> ddfreyne: feature request for cri: can we pretty please define flags as :foo_bar and have them automatically mapped to foo-bar? I hate the :'foo-bar' notation with a passion :)
alerante_ has quit [Remote host closed the connection]
<bobthecow> automatically categorized part of my posts based on the 12 most commonly used tags...
<bobthecow> then categorized all the rest with magic!
<bobthecow> the results were actually pretty good, too.
alerante has joined #nanoc
<ddfreyne> bobthecow: Hm, not sure how easy it is to do the cri change in a backwards-compatible way
alerante has quit [Ping timeout: 272 seconds]
jarr0dsz has joined #nanoc
jaspervdj has joined #nanoc
number-six has joined #nanoc
alerante has joined #nanoc
alerante has quit [Ping timeout: 246 seconds]
<guardian> hi
<guardian> $ nanoc compile -V │le-extension/?utm_campaign=iOS_Dev_Weekly_Issue_123&utm_medium=email&utm_
<guardian> cri (~> 2.3)
<guardian> WARN: Unresolved specs during Gem::Specification.reset: │source=iOS%2BDev%2BWeekly HTTP/1.1" 304 - 0.0013
<guardian> oops
<guardian> THIS
<guardian> $ nanoc compile -V
<guardian> cri (~> 2.3)
<guardian> WARN: Unresolved specs during Gem::Specification.reset:
<guardian> WARN: Clearing out unresolved specs.
<guardian> why do I get those warnings again? can't remember how I solved it last time
jarr0dsz has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jarr0dsz has joined #nanoc
VitamineD has joined #nanoc
jarr0dsz has quit [Quit: Textual IRC Client: www.textualapp.com]
pavelkunc has joined #nanoc
pavelkunc has quit [Quit: Leaving.]
jugglinmike has joined #nanoc
alerante has joined #nanoc
VitamineD has quit [Quit: VitamineD]
pavelkunc has joined #nanoc
VitamineD has joined #nanoc
louquillio has quit [Ping timeout: 246 seconds]
pavelkunc has quit [Quit: Leaving.]
louquillio has joined #nanoc
pavelkunc has joined #nanoc
pavelkunc has quit [Quit: Leaving.]
pavelkunc has joined #nanoc
VitamineD has quit [Ping timeout: 248 seconds]
tantalum has joined #nanoc
alerante has quit []
tantalum has quit [Ping timeout: 246 seconds]
tantalum has joined #nanoc
VitamineD has joined #nanoc
VitamineD has quit [Quit: VitamineD]
<guardian> re
<guardian> ddfreyne: do you remember how I can remove WARN: Unresolved specs during Gem::Specification.reset:
<guardian>       cri (~> 2.3)
<guardian> after having updated nanoc gem?
VitamineD has joined #nanoc
<ddfreyne> guardian: Hmmmmm
<ddfreyne> I vaguely remember something like that
<ddfreyne> guardian: does uninstalling cri work?
<ddfreyne> (all versions)
<guardian> ddfreyne: http://pastebin.com/qCSDmg4F that doesn't make much sense but now it's fixed
<ddfreyne> guardian: Hm, weird
<ddfreyne> Need some feedback on the new CONTRIBUTING document:
<ddfreyne> Quite a bit smaller; basically a cheat sheet that also references the web site
bghost has joined #nanoc
<guardian> when reporting bugs do you need the OS?
<guardian> and eventually the ruby version?
<ddfreyne> It can be very useful in figuring out what is wrong
<guardian> I can't see this mentioned in CONTRIBUTING.md nor on http://nanoc.ws/development/#reporting-bugs :)
<guardian> hmm actually http://nanoc.ws/development/#reporting-bugs mentions ruby version
<guardian> but not OS
<guardian> I typically have Windows/cygwin in mind
<ddfreyne> guardian: nanoc --version shows that
<guardian> oh ok
<ddfreyne> nanoc 3.6.7 © 2007-2013 Denis Defreyne.
<ddfreyne> Running ruby 1.9.3 (2013-02-22) on x86_64-darwin12.3.0 with RubyGems 2.1.11.
<guardian> indeed
<guardian> nanoc 3.6.7 © 2007-2013 Denis Defreyne.
<guardian> Running ruby 2.0.0 (2013-06-27) on x86_64-darwin12.4.0 with RubyGems 2.0.3.
<ddfreyne> Ooh Ruby 2.0.0 ;)
<guardian> uh, more recent ruby but older RubyGems
<ddfreyne> I should use that.
<bobthecow> aww crap
<bobthecow> sorry ddfreyne ^
<bobthecow> i'm used to hitting "edit" to get a pull request for a change.
<bobthecow> this time it committed directly to the repo :P
<bobthecow> want me to revert it and open a pull request?
<ddfreyne> bobthecow: Nah that is fine
<ddfreyne> Good suggestion though
ics has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
<bobthecow> the difference in the green button at the bottom wasn't enough to tip me off to the difference.
<bobthecow> "Commit changes" vs "Propose change"
<bobthecow> but i edit files directly on github just seldom enough that it made sense to me that clicking the button would commit the changes *to my fork* and let me open a pull request.
<ddfreyne> Yeah, that is a bit icky
ics has joined #nanoc
<ddfreyne> Time to install 2.0.0 (at last)
<bobthecow> ddfreyne: do it!
<bobthecow> we switch to 2.0.0 in production last week, so i've been running it locally for most things for the last month or so.
<ddfreyne> bobthecow: I was tempted to require Ruby 2.0.0+ for nanoc 4.0 once it's out
<ddfreyne> The lazy stuff could be *very* useful
<bobthecow> not a bad idea.
<bobthecow> nanoc 4.0 is still a bit far away, and 2.0.0 has been out what, six months now?
<ddfreyne> Yeah.
<ddfreyne> Might even use 2.1 features :P
<ddfreyne> File.fnmatch?("{foo,bar}", "foo", File::FNM_EXTGLOB)
<ddfreyne> New in 2.0 and something I really wanted.
<bobthecow> i thought there was a glob matcher in 1.9 also?
<ddfreyne> Yes, but it didn't support { }
<bobthecow> ahh. right.
<bobthecow> awesome.
ics has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
bghost has quit [Quit: leaving]
jarr0dsz has joined #nanoc
ics has joined #nanoc
tantalum has quit [Quit: Leaving]
pavelkunc has quit [Quit: Leaving.]
jarr0dsz has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]