Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Unable to save #151

MikeAdamowicz opened this Issue · 13 comments

8 participants


I'm on Windows 8.1 using Sublime Text build 3047 and Scout loaded with compass. The problem I'm encountering is that after about 1/2 hour to 45 min, I continually run into an error when trying to save the .scss file. See this image for the error details:

I believe that this is an issue with Scout because when I run compass on my ruby 2.0.0p247 (2013-06-27) [x64-mingw32], I can go along forever with no errors when trying to save the .scss file.

Admittedly a newbie to Github, I hope this is the correct place to list this.

Any help is much appreciated.


Confirm the issue


Hrm. I wonder if it's an issue with running compass vis-a-vis jruby since that's really all ScoutApp does.


It really seems to me like a Sublime issue, I can edit file in my FAR and save without any errors.
Found a suggestion to disable 'atomic_save' in Sublime, will try and post if it works


Yea looks like it solves it.
Got to Preferences (User) and add
"atomic_save": false


@AAverin, thanks for sharing your solution. I didn't even know atomic_save was a thing in Sublime.

@MikeAdamowicz, can you confirm this resolves your issue and close the issue if it does?


It resolve issue only partially - you have to wait a few seconds after editing before pressing Ctrl+S =) Our you will still get an error.
But at least I can work now=)


Damn. It's back=(
No idea why but seems to work for some time and now doesn't let me save again. Gonna keep going through sublime forums cuz other editors seem to work fine


Issue seems to be Windows 8 specific. Last year I have been using Scout+Sublime on Windows 7 - was working great.


+1 as well. Running Sublime Text 3 on Win 8.1 and setting "atomic_save" to false only changes what the error message says. I can still sort of work by pausing Scout while I save and then pressing play after, but it's not optimal whatsoever.


+1 same problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.