Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error Message: unbound variable $space #184

Open
dkebler opened this issue Aug 12, 2015 · 3 comments
Open

Error Message: unbound variable $space #184

dkebler opened this issue Aug 12, 2015 · 3 comments

Comments

@dkebler
Copy link

dkebler commented Aug 12, 2015

Now that I can compile your sass it is throwing errors in a three partials.

the error is
unbound variable $space
it happens in _forms, _progress, and _typography (in typography it throws same for $black) as well.

I am using libsass 3.2.5 the latest which is pretty identical these days to ruby sass although what you are doing in these files might be unsupported in libsass??? Here is the guide.
http://sass-compatibility.github.io/

@dkebler
Copy link
Author

dkebler commented Aug 13, 2015

This might be from creating that _kickstart.sass file that was basically _index.sass.

Maybe something is being set in your default theme (your entry to the core) avoids this error. Let me try this before you bother to look into it.

BTW, just so you understand I wish to use parts of kickstart without buying into to the whole framework, app and workflow so that is why I am trying to figure out if I can cherry pick certain partials and components.

@dkebler
Copy link
Author

dkebler commented Aug 14, 2015

So yes that was the issue
@importing your default theme as _kickstart.sass only pop two small errors.

from line 159 in your default theme

=alert($args...)
  +alert-default($args..)

your alert-default mixin has no arguments so it complained.
making this change fixes it

=alert($args...)
  +alert-default()

also in _direct_apply line 191
you have an "empty" tooltip-classes mixin with no body.
Maybe you intended to write it or remove this?
commenting it out fixes error.

If I am correct I can include this in the PR which now needs an update anyway.

@adamjgrant
Copy link
Owner

Thanks for walking through this. To be honest, I'm a little tied up with other life events at the moment to take this on, but I will add it to my queue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants