Open blokezero opened 8 years ago
Hi Alex,
Please give me a small example file that shows the issue.
On 27Nov 2015, at 08:30, Alex Sullivan notifications@github.com 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 https://github.com/bdkjones/CodeKit/issues/595.
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.
You have Libsass enabled, I'm assuming?
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: https://github.com/sass/libsass/issues/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.
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.
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 notifications@github.com 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.
Oh yes, I found that option in codekit - leaves Ruby Sass in the dust!
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!