sass index.sass index.css in command line gives error

[roguecartel]

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?

[Nathan Weizenbaum]

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.

--

You received this message because you are subscribed to the Google Groups "Haml" group.
To post to this group, send email to ha...@googlegroups.com.
To unsubscribe from this group, send email to haml+uns...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/haml?hl=en.

[roguecartel]

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 <nex...@gmail.com> 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 <timfong...@gmail.com> 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 ha...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > haml+uns...@googlegroups.com <haml%2Bunsu...@googlegroups.com>.

[Nathan Weizenbaum]

That suggests that index.sass doesn't exist where you're running the sass command. Are you sure it's there?

To unsubscribe from this group, send email to haml+uns...@googlegroups.com.

[roguecartel]

Hi, I checked again, sorry, I cleared and then grabbed the wrong error
-- here's the error:

>sass index.sass index.css --trace

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

On Dec 27, 7:04 pm, Nathan Weizenbaum <nex...@gmail.com> wrote:
> That suggests that index.sass doesn't exist where you're running the sass
> command. Are you sure it's there?
>

> > haml%2Bunsu...@googlegroups.com<haml%252Buns...@googlegroups.com>

[roguecartel]

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 <nex...@gmail.com> wrote:
> That suggests that index.sass doesn't exist where you're running the sass
> command. Are you sure it's there?
>

> > haml%2Bunsu...@googlegroups.com<haml%252Buns...@googlegroups.com>

[Nathan Weizenbaum]

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"?

To unsubscribe from this group, send email to haml+uns...@googlegroups.com.

[roguecartel]

Hmm...I am using RadRails, and so "dir" doesn't work because the
console wraps the shell as rails commands.

I went into an actual cmd console and changed the directory to the one
where sass exists.

That works.

I think I'd like to get compass working to do the automatic
watching...so, on to the next thing. At least, worse case, I can
manually process the .sass files as needed by going to the cmd
console.

Thanks.

On Dec 27, 7:57 pm, Nathan Weizenbaum <nex...@gmail.com> wrote:
> 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

> > > > haml%2Bunsu...@googlegroups.com<haml%252Buns...@googlegroups.com>
> > <haml%252Buns...@googlegroups.com<haml%25252Bun...@googlegroups.com>

[Nathan Weizenbaum]

If you're using Rails, you should really be using its automatic Sass-compiling. Why bother with running the command-line tool at all? Your stylesheets should be compiled automatically on each request.

To unsubscribe from this group, send email to haml+uns...@googlegroups.com.

[roguecartel]

Yah, I guess that's what I started out trying to do and when it wasn't
working, I tried to go in and see for myself manually what was going
on. When you mean automatic Saas-compiling, do you mean compass -
watch? My understanding was sass did not automatically compile.
Thanks!

On Dec 28, 11:34 am, Nathan Weizenbaum <nex...@gmail.com> wrote:
> If you're using Rails, you should really be using its automatic
> Sass-compiling. Why bother with running the command-line tool at all? Your

> > > > > > haml%2Bunsu...@googlegroups.com<haml%252Buns...@googlegroups.com>
> > <haml%252Buns...@googlegroups.com<haml%25252Bun...@googlegroups.com>
>
> > > > <haml%252Buns...@googlegroups.com<haml%25252Bun...@googlegroups.com>
> > <haml%25252Bun...@googlegroups.com<haml%2525252Bu...@googlegroups.com>

[Nathan Weizenbaum]

No, Sass does automatically compile when it's used as a plugin for a Ruby framework. On every request (in development mode) it checks all your Sass stylesheets and compiles them to CSS if they've been updated.

To unsubscribe from this group, send email to haml+uns...@googlegroups.com.

[roguecartel]

To use as a plugin, it is:

haml --rails path/to/rails/app

that would be from root? C:/Documents and Settings/..../app ?

On Dec 29, 9:24 am, Nathan Weizenbaum <nex...@gmail.com> wrote:
> No, Sass does automatically compile when it's used as a plugin for a Ruby
> framework. On every request (in development mode) it checks all your Sass

> > > > > > <haml%252Buns...@googlegroups.com<haml%25252Bun...@googlegroups.com>
> > <haml%25252Bun...@googlegroups.com<haml%2525252Bu...@googlegroups.com>
>
> > > > <haml%25252Bun...@googlegroups.com<haml%2525252Bu...@googlegroups.com>
> > <haml%2525252Bu...@googlegroups.com<haml%252525252B...@googlegroups.com>

[Nathan Weizenbaum]

It doesn't matter where you run that command, as long as the path you give goes to your application.

To unsubscribe from this group, send email to haml+uns...@googlegroups.com.