Mixin "with-grid-settings" does not accept a content block.
Trying to solve this, searched about it, but cannot find any info.
Thanks,
Ilia
It sounds like you might be trying to use an incompatible version of sass. If you are on Ruby 2.0, you should try upgrading your sass gem to 3.2.7.
Related
I have been pulling what hair I have left out. I just downloaded Codekit this week and want to redesign my own site using Compass/SASS/Susy. I have tried several ways to get it to work, the preference in Codekit to point at the executable path. I am really excited to get started on this new endeavor, but I can't seem to get by the setup. Any help would be greatly appreciated! Thanks.
Is your project set up correctly? Susy 2 requires SASS 3. CodeKit 2 has an option to use libSASS instead of SASS (I use it). There are other dependencies for which I use Bundler. If you use Bundler to set up your project, it will add 'require 'compass/import-once/activate' to your config.rb. Other than that, there is no specific need to require or import compass. Do you have a CodeKit error message that you can post to let us see what is going wrong?
I assume that you are using Susy 2. If you are using Susy 1 you must add #import "susyone"; to your config.rb. But I expect you know that already.
Re your comments:
Using Bundler, my Gemfile includes:
gem "susy", "~>2.1.0"
gem "sass", "~>3.3.0"
gem "breakpoint", "~>2.4.0"
so these must be installed on your system accessible to susy. CodeKit doesn't need compass but my config.rb file includes these:
require 'compass/import-once/activate'
require 'breakpoint'
require 'sassy-buttons'
obviously you may not be using sassy-buttons.
The documentation for Susy2 is extensive and is available at http://susydocs.oddbird.net/en/latest/. You don't say how you set up your project, but I assume that your CodeKit setup points to the correct files from SCSS to compiled CSS.
You need to '#import susy' in one of your .scss files. (I'm not sure that that is necessary anymore).
I am using version 1.9.0 of the RED HAWK IDE on RedHat 6.3.
After install RedHawk I looked at the video http://www.youtube.com/watch?v=wN9p8EjiQs4.
I tried to run through the example but I notice I am missing a large amount of the components she has like add_const_ff, complex_to, noise_source, vector_sink, medianfilter.
Should I have them? Is there a package I am missing?
Adding stuff to get the checker to except my question. I tried, then tried. Going to try.
Here you can find several packages from RedHawk developer:
https://github.com/Axios-Engineering
https://github.com/RedhawkSDR
You can try to download and build them
All of the components you mentioned except for the medianfilter are part of the GNUHawk library of components and can be found at https://github.com/RedhawkSDR/integration-gnuhawk/tree/master/components.
The median filter is part of the basic-components library and can be found at https://github.com/RedhawkSDR/basic-components
I tried to build the example package from here but sadly I get following error:
error: Couldn't find package std in any of the workspaces in the RUST_PATH (C:\U
sers\User\Desktop\test\hello.rust:C:\Users\User\Desktop\test\hello:C:\Users\Use
r.rust)
Now it's kinda obvious that there is some issue with RUST_PATH but I am somewhat unable to find documentation concerning it.
note: I'm using Windows 8 64 bit and Rust 0.8
Rustpkg has been removed from basic library and moved into librustpkg.
There are alternatives like Makefile or CMake, but I assume the preferred version it's using cargo-lite.
My advice is just look at Rust-CI for a project that uses package manager you like most and copy it's build shamelessly.
UPDATE: A new package manager for rust has been announced. It's called Cargo. We'll see how it works out, but that is possible future default.
Rustpkg has been removed from Rust. Hopefully we will get something to replace it.
Is there a FormAlchemy alternative for Python3.2? I'm specifically interested in using it in conjunction with Pyramid.
I'm getting syntax errors when setting up FormAlchemy1.3.3 so their latest release is not compatible.
At time of writing there is none
OSX 10.6
CoffeeScript 1.2.0
node.js v0.7.7-pre
I am seeing a deprecation notice every time I run the coffee command. The notice is this:
path.exists is deprecated. It is now called `fs.exists`.
I know that this is happening because node.js deprecated path.exists. See
https://github.com/joyent/node/pull/2587
I would think there would be a lot of info about this but all I can see is some indirect reference relating to a more serious issue saying it's not going to be 'fixed':
https://github.com/jashkenas/coffee-script/issues/2113
Am I the only one having this problem? Does anyone have a suggestion on how I can make this go away?
https://github.com/jashkenas/coffee-script/blob/master/lib/coffee-script/command.js#L323
There are references to path.exists in the coffeescript source code.
Note that that in node 0.6 (the current stable version) fs.exists is null so it's difficult to cleanly upgrade this.
We have an issue where the same source code doesn't work in both 0.6 and 0.7.
I would assume that we wait for 0.8 and then someone will upgrade coffeescript to use fs.exists and deprecate 0.6 support
When waiting for 0.8, on OSX you can temporary fix this issue by replacing all path.exists to fs.exists in file (if you install globally):
/opt/local/lib/node_modules/coffee-script/lib/coffee-script/command.js
Don't forget to use root access when editing.
This is a bit of a late answer, but there is a patching module meant to temporarily fix this problem until everyone has a chance to update there code.
https://github.com/SportZing/node-exists-patch
Couldn't you just change all the instances of that in the source code?