louquillio has quit [Remote host closed the connection]
louquillio has joined #nanoc
bghost has quit [Ping timeout: 256 seconds]
louquillio has quit [Remote host closed the connection]
louquillio has joined #nanoc
louquillio has quit [Remote host closed the connection]
whk has left #nanoc [#nanoc]
louquillio has joined #nanoc
<ddfreyne>
bobthecow: I’ll just ignore the Giant Robot Software site. I can’t be arsed to write them a proper mail. I’ll just call it flattery :)
<guardian>
?
<guardian>
oh I see...
<ddfreyne>
gem install guard-nanoc
<ddfreyne>
Works now :D
<darix>
ddfreyne: just let your lawyer send the mail ;)
<ddfreyne>
darix: meh ;)
<ddfreyne>
So you can consider watch/autocompile to be officially deprecated from now on
<guardian>
meh
<guardian>
so we're not supposed to run nanoc watch anymore
<guardian>
so we remove gem 'listen', gem 'rb-fsevent', '~> 0.9' and gem 'rb-inotify', '~> 0.9' and add gem 'guard-nanoc'
<guardian>
then what?
<ddfreyne>
`guard init nanoc`
<ddfreyne>
edit Guardfile if necessary, add and commit it
<ddfreyne>
`guard`
<ddfreyne>
and that’s it
<guardian>
meh
<guardian>
another file :)
<guardian>
well if you say it's a better solution than watch, I trust you
<guardian>
so I added 'guard-nanoc' to my Gemfile… but I don't have guard unless I also add (and install) gem 'guard'. I find it idiotic. When you want guard-nanoc it should be transitive. Of course you want guard too.
<ddfreyne>
Hmm, guard-nanoc should depend on guard indeed!
<guardian>
I really thought it was the way gem worked (for some reason related to listen not listing its dependencies on rb-inotify or rb-fsevent)
<guardian>
and that behaviour they chose, that is "list your deps explicitly" I find it idiotic. because always depending on rb-inotify and rb-fsevent is harmless
<guardian>
I don't undertand why they do that
<ddfreyne>
guardian: Listen is an exception… it cannot have dependencies on rb-inotify, rb-fsevent, … because those gems are platform-specific
<guardian>
may be to cut down gem install time…
<guardian>
but really, installing rb-inotify and rb-fsevent always does'nt take long
<ddfreyne>
They’re not cross-platform, so e.g. on Windows you cannot install them at all
<guardian>
compared to googling for why they did that :)
<guardian>
I read the contrary!
<guardian>
I read you can install them
<guardian>
and they just do nothing
<guardian>
they just won't be used
<guardian>
and I installed rb-inotify on the mac, it just does nothing. I prefer putting both rb-inotify and rb-fsevent and commit Gemfile than fiddling with the dependency I want depending on the machine I run nanoc
<guardian>
-----
<guardian>
14:05:34 - INFO - Guard here! It looks like your project has a Gemfile, yet you are running
<guardian>
> [#] `guard` outside of Bundler. If this is your intent, feel free to ignore this
<number-six>
Error: <hint>:1:3: parse error on input `]'
<guardian>
so? feel free to ignore this?
<ddfreyne>
`bundle exec guard` is the recommended way
<guardian>
it fails
<guardian>
guard is not part of the bundle :)
<guardian>
guess it's related to the missing dep
<ddfreyne>
Ahh, you should add guard to the Gemfile explicitly
<guardian>
well isn't that what we started with?
<guardian>
if guard-nanoc depends on guard
<guardian>
do I need to add guard to my Gemfile?
<ddfreyne>
Nope, but guard-nanoc doesn’t depend on guard yet
<ddfreyne>
(it will in 1.0.1 :P)
<guardian>
I expect the answer to be NO. but I suspect the guard-nanoc gem needs to be updated for that first :)
<ddfreyne>
Indeed
<guardian>
damn now that my site is up, I'm all "now what?"
<ddfreyne>
:D
<guardian>
not much people read it (which I can understand since I'm not a superstar like <pick your favorite superstard, e.g. Scott Hanselman, Jeff Hatwood, John Gruber, etc.>
<guardian>
)
bghost has joined #nanoc
bghost has quit [Changing host]
bghost has joined #nanoc
Segismond has joined #nanoc
Segismond_ has quit [Ping timeout: 246 seconds]
<ddfreyne>
guardian: Same here… I even don’t blog a lot (once every 3 years, apparently)
<guardian>
:)
bghost has quit [Read error: Connection reset by peer]
bghost has joined #nanoc
bghost has quit [Quit: leaving]
bghost has joined #nanoc
bghost has joined #nanoc
bghost has quit [Changing host]
bghost has quit [Client Quit]
bghost has joined #nanoc
bghost has joined #nanoc
bghost has quit [Changing host]
<ddfreyne>
Whee… not that I want to make anybody jealous, but the identifiers in my version of nanoc allow me to do this:
<ddfreyne>
compile '/assets/style/*.sass' do ; filter :sass ; end
<ddfreyne>
passthrough '/assets/fonts/*.eot'
<ddfreyne>
:D
louquillio has quit [Remote host closed the connection]
<ddfreyne>
route '/assets/style/*.sass' do ; item.identifier.with_ext('css') ; end