-
Notifications
You must be signed in to change notification settings - Fork 19
Compass Build not working on Mac #40
Comments
You are right. Tested it. Isn't building for me too. I'm looking up the problem. |
Okay. I can verify it's working in Sublime Text 2, but not in Sublime Text 3. Since the package folder was changed and the packages get compiled (as far as I see), I cannot debug this as quickly as for Sublime Text 2. I need to get more information about the changes made in Sublime Text 3 before I can patch this. Or someone who has already contributed to the package have an idea. @CristinaSolana @drwlrsn |
@changalberto Please test #42 - it should fix this issue. |
Thanks for this. But it's not fixing the problem with Sublime Text 3 (which is not your fault, because I've made tests back with version 1.0.7 and it seems the package never worked with Sublime Text 3). I'm going to rename this issue since it isn't package version specific, but more Sublime Text version specific. |
Just now, i found the Compass pluins is not running in ST2. ST2's control console the error 'not found build.sh'. |
I can confirm that. Seems to have the same problem like Sublime Text 3 now. No console output. No build errors. Nothing happens. |
Okay, I may have to take myself out of this tests. I downloaded 1.0.7 too and it's not working for me and I guess this could be because of my RVM setup. Yesterday, I've got several version running without problems. |
Yesterday it was working very well, but in the morning , I git clone your Compass source to my sublime text 2 packages and open sublime text 2 for coding. I can see it was not worked, The help information was display in console "[[ not found". |
My OS is Ubuntu, I can use old version(in My win7 OS Sublime-Text-2-Compass-Build-System) to my ST2 package and it is working. |
@hankewins I've merged @attila 's Pull some minutes ago. Try if it's fixing your problem. It seems you have a different problem than @changalberto is describing, since he's not even getting a error message in the console. |
Okay thanks! I will retry test for the problem and get the answer. |
@Nachtmeister There's one more issue — it doesn't like reading directory path with spaces at the moment... |
@changalberto Thanks. Yes, there was an issue #44 created right now. |
On a quick look:
No build error,
No compile messages in console.
Tried removing the package and reinstalling and restarting.
I think it's not recognizing my config.rb at the root of the project.
My sass files live in subdir public/assets/styles/sass/
The text was updated successfully, but these errors were encountered: