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

Several errors after rake generate on _syntax.scss #1

Open
gtcarlos opened this issue Mar 4, 2014 · 4 comments
Open

Several errors after rake generate on _syntax.scss #1

gtcarlos opened this issue Mar 4, 2014 · 4 comments

Comments

@gtcarlos
Copy link

gtcarlos commented Mar 4, 2014

Hello,

I'm trying to install the theme (using submodule install) into my blog but after

rake install['MediumFox']

When I try to rake generate I've got the following errors:

## Generating Site with Jekyll
directory source/stylesheets/base/bootstrap/ 
WARNING on line 74 of /home/gtcarlos/Blog/octopress2/sass/base/_syntax.scss: "html .gist .gist-file .gist-meta" failed to @extend ".sans".
  The selector ".sans" was not found.
  This will be an error in future releases of Sass.
  Use "@extend .sans !optional" if the extend should be able to fail.

WARNING on line 96 of /home/gtcarlos/Blog/octopress2/sass/base/_syntax.scss: "pre" failed to @extend ".mono".
  The selector ".mono" was not found.
  This will be an error in future releases of Sass.
  Use "@extend .mono !optional" if the extend should be able to fail.

WARNING on line 112 of /home/gtcarlos/Blog/octopress2/sass/base/_syntax.scss: "p code" failed to @extend ".mono".
  The selector ".mono" was not found.
  This will be an error in future releases of Sass.
  Use "@extend .mono !optional" if the extend should be able to fail.

WARNING on line 112 of /home/gtcarlos/Blog/octopress2/sass/base/_syntax.scss: "li code" failed to @extend ".mono".
  The selector ".mono" was not found.
  This will be an error in future releases of Sass.
  Use "@extend .mono !optional" if the extend should be able to fail.
@camdez
Copy link
Contributor

camdez commented Mar 7, 2014

I get the same (using the other installation method). Though it's probably worth noting that those are warnings, not errors.

@bertuz
Copy link

bertuz commented Mar 23, 2014

I got the same, everything seems to be OK though

@Jacubeit
Copy link

same here, works fine, but a little confusing in terminal

@alexeyza
Copy link

alexeyza commented May 8, 2014

same here.

@lmm lmm mentioned this issue May 9, 2014
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

5 participants