Created
December 10, 2010 20:14
-
-
Save doctyper/736729 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
$ compass compile path/to/sass/ --trace | |
ArgumentError on line 95 of /Library/Ruby/Gems/1.8/gems/compass-0.11.alpha.4/lib/compass/compiler.rb: wrong number of arguments (3 for 2) | |
/Library/Ruby/Gems/1.8/gems/compass-0.11.alpha.4/lib/compass/compiler.rb:95:in `compile_if_required' | |
/Library/Ruby/Gems/1.8/gems/compass-0.11.alpha.4/lib/compass/compiler.rb:82:in `run' | |
/Library/Ruby/Gems/1.8/gems/compass-0.11.alpha.4/lib/compass/compiler.rb:80:in `each' | |
/Library/Ruby/Gems/1.8/gems/compass-0.11.alpha.4/lib/compass/compiler.rb:80:in `run' | |
/Library/Ruby/Gems/1.8/gems/compass-0.11.alpha.4/lib/compass/compiler.rb:103:in `timed' | |
/Library/Ruby/Gems/1.8/gems/compass-0.11.alpha.4/lib/compass/compiler.rb:79:in `run' | |
/Library/Ruby/Gems/1.8/gems/compass-0.11.alpha.4/lib/compass/commands/update_project.rb:36:in `perform' | |
/Library/Ruby/Gems/1.8/gems/compass-0.11.alpha.4/lib/compass/commands/base.rb:18:in `execute' | |
/Library/Ruby/Gems/1.8/gems/compass-0.11.alpha.4/lib/compass/commands/project_base.rb:19:in `execute' | |
/Library/Ruby/Gems/1.8/gems/compass-0.11.alpha.4/lib/compass/exec/sub_command_ui.rb:43:in `perform!' | |
/Library/Ruby/Gems/1.8/gems/compass-0.11.alpha.4/lib/compass/exec/sub_command_ui.rb:15:in `run!' | |
/Library/Ruby/Gems/1.8/gems/compass-0.11.alpha.4/bin/compass:25 | |
/Library/Ruby/Gems/1.8/gems/compass-0.11.alpha.4/bin/compass:39:in `call' | |
/Library/Ruby/Gems/1.8/gems/compass-0.11.alpha.4/bin/compass:39 | |
/usr/local/bin/compass:19:in `load' | |
/usr/local/bin/compass:19 |
Yes. You can still do that by using this function directly like you were before with sprite-image()
http://beta.compass-style.org/reference/compass/helpers/sprites/#sprite
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Well, it's different from spacing in that Lemonade offsets the image by your passed-in y-value.
For example, if you gave it a y-offset of 3, it would position the image beginning 3 pixels from the top. The spacing parameter pads the area between each sprite, but still positions the image flush with the top of the element.
Am I making sense?