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

SCSS - @warn and @debug missing from log output #595

Open
blokezero opened this issue Nov 27, 2015 · 7 comments
Open

SCSS - @warn and @debug missing from log output #595

blokezero opened this issue Nov 27, 2015 · 7 comments

Comments

@blokezero
Copy link

Maybe I was tripping but I'm sure these directives used to output to the log on compilation?

I've checked through the options and can't find it as a setting.

Very handy for checking breakpoint values etc.

Thanks!

@bdkjones
Copy link
Owner

Hi Alex,

Please give me a small example file that shows the issue.

On 27Nov 2015, at 08:30, Alex Sullivan [email protected] wrote:

Maybe I was tripping but I'm sure these directives used to output to the log on compilation?

I've checked through the options and can't find it as a setting.

Very handy for checking breakpoint values etc.

Thanks!


Reply to this email directly or view it on GitHub bdkjones/CodeKit#595.

@blokezero
Copy link
Author

Here you go:
test.scss.zip

It just has:

$red: #e4003a;
@debug $red;

and if you run:

$ sass test.scss

You see that sass prints the value to the standard error output stream - if I could see that in the codekit log view it'd save me hopping back to the command line.

@bdkjones
Copy link
Owner

bdkjones commented Dec 9, 2015

You have Libsass enabled, I'm assuming?

@bdkjones
Copy link
Owner

bdkjones commented Dec 9, 2015

It looks like Libsass is currently hard-coded to spit these warnings to stderr, which means I can't intercept them and display them in the UI. I've opened this as a request on the Libsass repo: sass/libsass#1779

When/if they implement it, I'll be able to capture those warnings and show them in the UI. Until then, you can see them by opening console.app and looking for them there when the file is compiled.

@blokezero
Copy link
Author

Thanks Bryan - actually I just installed sass as a Ruby gem, so I don't think it's Libsass, but I guess that is the underlying tech.

@bdkjones
Copy link
Owner

bdkjones commented Dec 9, 2015

Oh god. Don't use Ruby sass. Flip on Libsass in CodeKit; it will change your life.

Sent from my iPhone

On Dec 9, 2015, at 01:51, Alex Sullivan [email protected] wrote:

Thanks Bryan - actually I just installed sass as a Ruby gem, so I don't think it's Libsass, but I guess that is the underlying tech.


Reply to this email directly or view it on GitHub.

@blokezero
Copy link
Author

Oh yes, I found that option in codekit - leaves Ruby Sass in the dust!

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