Closed rogerbraun closed 12 years ago
Hi @rogerbraun
At a first glance it looks like blazing is reading it's config file before it is even created. I'll have a closer look at it ASAP, thanks for the feedback!
I changed config.rb to say this:
config.instance_eval(File.read(config.file)) if File.exists?(config.file)
I also had to add require 'erb'
to commands.rb, else I would get an error about ERB not being defined.
With these changes, the command runs and gives the expected result.
Oh, and thank you for your quick reaction!
You're welcome!
I think this could be fixed by not requiring the whole config object in the init command (I think it's kind of ok if config loading fails when no file is around... blazing itself should know better than to load it before it even created the file). But I have no workstation with git etc. available tonight, so it'll have to wait until tomorrow. Hope you can live with your own workaround for now.
Just released 0.2.13, hope the fix works for you.
Cheers
I did a
gem install blazing
, followed byblazing init
. This ist the result:I tried using the current version by adding
gem 'blazing', :git => 'git://github.com/effkay/blazing.git'
to my Gemfile, but the results ofbundle exec blazing init
are the same.My Ruby version is "ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]".