Question. Do I need to install libsass first to get this to work? I'm working on a MacBook Pro with OS X 10.9.5 running

Is there a way to configure the output path?

Hey, plugin was great but now when I hit save, coda crashes and nothing gets saved or compiled to css. Can you help?

Error attached

Can also send you the real error txt file if you need it.

Thanks!

Tom

Hey there!

Great plugin, the only problem I find is that using the Nested Output style I get the closing brace for each class beside the last property instead of a new line.

Also, I'm used to do tabbing to have a nested code and the plugin uses two blank spaces.

Have you thought about adding some options to configure this in the future?

Thanks,
Juan.

This is a great concept... However, since it leaves in all spacing, comments, etc., the output is not really suitable for production use (which should really be minified with comments stripped out). Unfortunately until that's addressed I don't see how this is actually very useful; if an alternative Sass compiler has to be run before uploading to a production server, one may as well just use that alternative all the time.

when I edit my files the font-conversion goes from "'maps-navigation': "\e889", to content:  (should be "\e889"). Seems some processing cant figure out "\e889"?

Hi,

I noticed that Coda 2 does not recognize when the css file generated has been updated after saving the scss file. This makes it difficult when using the publish feature, as I can publish the scss file but have to manually file transfer my new generated css file.

Is there a setting?

Thanks!

On my site, I have a /css folder, and all the Sass files are in /css/scss.

When I save style.scss (in /css/scss) it generates style.css and style.map and outputs to the /css folder (which is fine) but the source map is linked to "../style.map".

OS X Yosemite 10.10
Plugin Version 3.0.0

Gif showing the issue:

I would like to use a mixin for the CSS calc function so that the various browser prefixed would be attached. Unfortunately the following mixin will not be compiled correctly:

@mixin calc($property, $expression) {
  #{$property}: -moz-calc(#{$expression});
  #{$property}: -webkit-calc(#{$expression});
  #{$property}: calc(#{$expression});
}

if I call the mixin like @include calc(width, "(50% - (227px / 2))"); the output for the last line will be:

width:calc(#{$expression});

I'm totally new to scss and I installed the plugin in Coda. It works great when I am working locally. But when I save a scss file in the FTP directly on the server, no .css file is spawning.

So I wonder if this plugin automatically generates a css file locally and unable to automatically generate a css file directly on the server from a scss file on the server.

Thanks in advance!

This is a great enhancement to Coda, but until certain other features are added, it would be great to easily disable it so I can use another application to compile at times.

I'm running a MacBookPro 1,2 with OS10.6.8 and the plugin 'installs' without any errors but it doesn't function and doesn't show up in the 'Plugins' menu within Coda2. At first I thought it just didn't install for some reason so I double clicked the plugin again and Coda said the plugin was already installed and gave me the option to replace it.

Is my system just too old to run this plugin?

Thanks!

When trying to use this in macOS 10.15, I get the following error:

“Sass.codaplugin” cannot be opened because the developer cannot be verified.
macOS cannot verify that this app is free from malware.

Is there anything we can do to get around this?

A great plugin but any chance of implementing a solution that can include Compass? I'd much rather this plugin over using scout.

In v3, using Compressed output style, plugin doesn't compile media querys. No problems i v2.

I installed it by clicking but no plugin appears inside the app. Does it add a context menu somewhere?

Hi,

thank for the great plugin, I'm trying to use random($limit) to get random number but its not working :(

Any ideas?

Thank you!
Davor

If I create an inline comment on a new line, after a comma, the scss won't compile and an error occurs.

I've been using this plugin for the better part of a year across numerous scss files and this has suddenly started happening. Is this due to the most recent update?

If the plugin is disabled it can be dealloc'd which then will cause a crash because it's still a registered observer of the save notification. It needs to unregister in dealloc.

Furthermore, it should be using the callback available in 2.0 and later:

• (void)textViewWillSave:(CodaTextView*)textView

Instead of sniffing private notifications.

When I try to use the plugin in coda2.... It tells me it can not work with or recognize the @extend, @opacity, @include and others.

Is there a fix for this, or do I need ot delete those @tags and add them back in via css proper code....

Why can you not save the CSS files in another folder?

Is there a way to compress the output .css file on the most compressed option, but keep comments in tact? I use this for a lot of wordpress builds where the comments area is required at the top.

I was struggling with using a mixin, and then realized that Bourbon is a bit outdated. It looks like selection was added a few days after Bourbon was added to the plugin. I'm sure there are probably more missing that I haven't found yet.

What about supporting Bourbon, Neat, Compass, etc. mixin libraries as part of the compile process?

http://bourbon.io/

Sass have been updated with some new feathers and I wonder if this plugin will be updated too

Is there any way of triggering Coda's auto-refresh with this? Ideally it would behave exactly like editing the CSS file directly, where it updates as soon as you type, but failing that, refresh on save of the SASS file would be cool.

Currently it seems you need to manually refresh the preview pane to see any changes which slows the whole thing down a lot.

Maybe it could somehow utilise takana or something?

Would be great to have 'expanded' as an option for compile.

Hey, thanks for the plugin!
However, the Plugin only works locally for me, am i missing something?

I just discovered this plugin exists (fantastic BTW) and have run into this inconvenience.

I saw someone else had this issue https://github.com/keegnotrub/coda-sass-plugin/issues/4 (now closed) and you said it was resolved in Code v2.5. I'm using v2.5.11 and on save it registers the scss just not the css.

Is there a setting I'm not aware of? It's obviously not critical, I was just wondering if I'm missing something.

Thanks in advance.

Hi there,

Great plugin - I use it all of the time.

Not sure if this is the right place for this request but:

How difficult would it be to add an option to exclude the automatic compiling of the SASS on a per-Coda Project basis?

The reason I ask is that in some cases, I create the CSS via a gulpfile, whereas other times I use this plugin.

When using a gulpfile, I get an erroneous CSS file output that I have to delete after each save, and then I run the gulpfile to create the one I want.

The ability to just say "Don't use this plugin for this project - Remember this setting" would be great.

Anyway, thanks for this plugin!

I'm not able to enact a compile by saving a .sass file. My scss file can pull in sass includes, but for some reason I can't initiate a compile by saving a .sass file.

Is it a difficult matter to make it work with either file types?