If you're using the command-line utility, the index.sass file has to be in the same directory from which you're running the "sass" command. What's the output of "dir"?
On Sun, Dec 27, 2009 at 7:38 PM, roguecartel <[email protected]> wrote: > Nope, I was right the first time, there is an index.sass and I removed > the 264-266 lines....hmmm....here is the error again. > > Can I keep the index.sass file in the css file or do I need to > designate a different folder? > > sass index.sass index.css --trace > c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/../lib/haml/exec.rb: > 108:in `initialize': No such file or directory - index.sass > (Errno::ENOENT) > from c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/../lib/haml/ > exec.rb:108:in `open' > from c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/../lib/haml/ > exec.rb:108:in `open_file' > from c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/../lib/haml/ > exec.rb:93:in `process_result' > from c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/../lib/haml/ > exec.rb:190:in `process_result' > from c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/../lib/haml/ > exec.rb:246:in `process_result' > from c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/../lib/haml/ > exec.rb:22:in `parse!' > from c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/sass:8 > from c:/ruby/bin/sass:19:in `load' > from c:/ruby/bin/sass:19 > > On Dec 27, 7:04 pm, Nathan Weizenbaum <[email protected]> wrote: > > That suggests that index.sass doesn't exist where you're running the sass > > command. Are you sure it's there? > > > > On Sun, Dec 27, 2009 at 6:53 PM, roguecartel <[email protected]> > wrote: > > > Hi, I'm still getting an error and can't seem to parse it: > > > > > c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/../lib/haml/exec.rb: > > > 108:in `initialize': No such file or directory - index.sass > > > (Errno::ENOENT) > > > from > c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/../lib/haml/ > > > exec.rb:108:in `open' > > > from > c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/../lib/haml/ > > > exec.rb:108:in `open_file' > > > from > c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/../lib/haml/ > > > exec.rb:93:in `process_result' > > > from > c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/../lib/haml/ > > > exec.rb:190:in `process_result' > > > from > c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/../lib/haml/ > > > exec.rb:246:in `process_result' > > > from > c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/../lib/haml/ > > > exec.rb:22:in `parse!' > > > from c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/sass:8 > > > from c:/ruby/bin/sass:19:in `load' > > > from c:/ruby/bin/sass:19 > > > > > On Dec 24, 11:33 am, Nathan Weizenbaum <[email protected]> wrote: > > > > Something's going wrong with your loading of Sass. Open up > > > > c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16//lib/haml/exec.rb and > remove > > > > lines 264, 265, and 266 and try again. You'll still get an error, but > > > this > > > > one will make more sense. > > > > > > I've pushed a change to master and stable that should cause error > > > messages > > > > like this to be displayed properly by default. > > > > > > On Thu, Dec 24, 2009 at 11:04 AM, roguecartel <[email protected]> > > > wrote: > > > > > Hi, > > > > > > > I am trying to get up and running on sass and compass. To try it > out, > > > > > I type the following: > > > > > > > >>sass index.sass index.css --trace > > > > > > > I got the following output: > > > > > > > c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/../lib/haml/exec.rb: > > > > > 264:in `process_result': uninitialized constant Sass (NameError) > > > > > from > c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/../lib/haml/ > > > > > exec.rb:22:in `parse!' > > > > > from c:/ruby/lib/ruby/gems/1.8/gems/haml-2.2.16/bin/sass:8 > > > > > from c:/ruby/bin/sass:19:in `load' > > > > > from c:/ruby/bin/sass:19 > > > > > > > >sass -v > > > > > Haml/Sass 2.2.16 (Powerful Penny) > > > > > > > >gem -v > > > > > 1.3.5 > > > > > > > Help? Am I missing something? > > > > > > > -- > > > > > > > You received this message because you are subscribed to the Google > > > Groups > > > > > "Haml" group. > > > > > To post to this group, send email to [email protected]. > > > > > To unsubscribe from this group, send email to > > > > > [email protected]<haml%[email protected]> > <haml%[email protected]<haml%[email protected]> > >< > > > haml%[email protected]<haml%[email protected]> > <haml%[email protected]<haml%[email protected]> > > > > > >. > > > > > For more options, visit this group at > > > > >http://groups.google.com/group/haml?hl=en. > > > > > -- > > > > > You received this message because you are subscribed to the Google > Groups > > > "Haml" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<haml%[email protected]>< > haml%[email protected]<haml%[email protected]> > >. > > > For more options, visit this group at > > >http://groups.google.com/group/haml?hl=en. > > > > > > -- > > You received this message because you are subscribed to the Google Groups > "Haml" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected] <haml%[email protected]>. > For more options, visit this group at > http://groups.google.com/group/haml?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/haml?hl=en.
