-
Notifications
You must be signed in to change notification settings - Fork 217
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
[Windows 7] Problem when saving Sass file #14
Comments
Which version of windows are using, and what are you using for a terminal (i.e., git-bash, cygwin, linux subsystem for windows?) |
I'm on Windows 7 Professional SP1, and I used both Git Bash (first image) and VS Code integrated terminal - bash (last two images) |
I'll have to try this out on a VM when time permits. Windows 7 SP1 ended its mainstream support period in 2015, and there are some nuances around native code like |
I have the same problem on Windows 10 + VSCode. :( |
Hi guys, I don't know if this is the correct place to post it (I'm new to both GitHub and FrontEnd Masters), but anyways:
I have a problem that whenever I save my Sass file (app.scss from Exercise 1), the Git Bash gives me an error... See attached screenshot for exact message.
I'm not sure whether it is a problem with Node, Sass compiler, VS Code or with the course's application!
PS: Node version is v6.9.5
PS2: @mike-north Do the FE Masters' courses have a forum or similar place where the students are able to chat and give feedback? Maybe a Slack channel?
Would you guys help me? :)
Thanks a bunch!
Edit
Now when doing Exercise 2 and using the VS Code embed terminal (bash), I get the error with the added info that a Segmentation Fault ocurred... First .scss save worked fine, but the second threw this:
Edit 2
I keep getting errors, and they differ each time... this time (exercise 4) it was:
I found https://github.com/olefredrik/FoundationPress/issues/731 and it might be the solution, but I'm clueless about where I should make use of gulp-wait or change my VS Code saving settings?
The text was updated successfully, but these errors were encountered: