Installing SASS on Windows
In this post, I introduced some of the powers of SASS language, and I left the rest of the exploration to you, because I didn’t really go deep yet. But first you need to install it on your system to use it of course.
In their website, they explained how to install it on Linux and MacOS, and mentioned how to install on a Windows system but i needed to figure it out because before that, I never had a relationship with Ruby. And lucky me(!), SASS uses Ruby to operate.
Let me explain what I did.
First get the latest Ruby installer here : http://rubyinstaller.org/downloads/
Second, double click and start the installati
on, accept the licence agreement, and on the second page, check all of the checkboxes and click Install.
When the installation finishes, open a Command Prompt window (Win+R then type “cmd” and press enter)
Then type this:
ruby -S gem install sass
and wait for the script to install SASS. (It feels like using apt-get or yum :P). when you finish installing SASS, type this:
sass --help
and if you see a list of parameters and explanations, then your SASS is ready to be used.
FCKEditor “Dialog Width” Correction in Firefox
jQuery Scrolite Plugin
Saving passwords submitted by jQuery $.post function
About The Author
Taha Paksu
hello
you need to install sass, not sass-rails.
did you add the ruby path to your environment variables?
Click Control Panel | System Properties | Environment Variables.
Under System Variables, select Path and click EDIT.
Add your Ruby directory to the end of the Variable Value list and click OK.
I typed ruby -S gem install sass in cmd
‘ruby’ is not recogonized as an internal or external command
operable program or batch file
Please help
Hi I am getting this error
C:Ruby193bin>gem install sass-rails
ERROR: Could not find a valid gem ‘sass-rails’ (>= 0) in any repository
ERROR: While executing gem … (Gem::RemoteFetcher::FetchError)
Errno::ETIMEDOUT: A connection attempt faile
I had the same problem. You need to go to Start -> locate the Ruby folder and run Ruby command line instead of the Windows one. It worked for me!