New names for the Susy +columns() mixin

columns.scss

// This must be an old conflict, but I never noticed it until today:
//
// w3c      : http://www.w3.org/TR/css3-multicol/#columns0
// Compass  : http://compass-style.org/reference/compass/css3/columns/
// Susy     : https://github.com/ericam/susy/blob/master/REFERENCE.mkdn#mixins
//
// In the w3c spec, 'columns: $number' can be used to split content into a $number of columns.
// Compass has a CSS3 'columns()' mixin, that works with the w3c spec.
// In Susy, we have a competing 'columns()' mixin that _spans_ columns rather than _splitting_ them.
//
// Time for an API name change! 
//
// Between these three, I lean strongly towards the clarity of #3.
// But you might have even more ideas...?

/* 1. short */
@include cols(2);

/* 2. name-spaced */
@include susy-columns(2);

/* 3. clarified (by Chris Eppstein) */
@include span-columns(2);

just ran into this exact conflict when attempting to use compass columns mixin in conjunction with my susy grid layout.
What would be the best way to resolve this issue for my current project until this is fixed?
Anyone care to help a bloody compass beginner?

@memetical You can either upgrade to 1.0.alpha.1 (check the changelog for upgrade instructions), or you can use the long-form properties as listed here: http://compass-style.org/reference/compass/css3/columns/ (column-count, column-gap, etc).

@pdewouters You're not thinking this through clearly. Nouns are more appropriate to variables. For most clarity we should use an active but incomplete sentence:

@include please-adjust-the-susy-grid-span-columns-count-of-this-element-to();
@include thank-you-kindly();

The latter doesn't do anything, but is necessary for proper manners.

@include bridge(); @include occupy();

@ericam thanks, didn't realize that!