sass-twitter-boostrap in Sass instead of Scss
Closed this issue · 7 comments
Hey guys. I probably haven't spent enough time looking for an answer, but I actually want to use the sass-twitter-bootstrap in the Sass syntax instead of Scss.
I tried sass-convert but it broke most or all of the files because of how the comments are formatted. It looks like sass-convert doesn't deal with /* comment */ on one line after code.
Has anyone else accomplished using this with Sass instead of Scss?
That's a pity that sass-conver doesn't handle these comments well. It would probably be good to file an issue on the Sass project.
What's your motivation for wanting bootstrap in the Sass syntax? Sass understands both syntaxes.
--John
On May 27, 2013, at 2:32 PM, Ryan Burnette notifications@github.com wrote:
Hey guys. I probably haven't spent enough time looking for an answer, but I actually want to use the sass-twitter-bootstrap in the Sass syntax instead of Scss.
I tried sass-convert but it broke most or all of the files because of how the comments are formatted. It looks like sass-convert doesn't deal with /* comment */ on one line after code.
Has anyone else accomplished using this with Sass instead of Scss?
—
Reply to this email directly or view it on GitHub.
I think sass-convert is its own thing. I'm going to see if I can submit an issue about it specifically.
I thought the Sass compiler would freak out if I gave it a mix of files in both syntaxes. The last time I tried that it didn't appear capable of handling such. So I tried to convert over to all Sass syntax for that reason. I'll revisit the prospect of having a project mixed across the two syntaxes.
The core motivation is that I want to write in Sass instead of Scss on my next project.
Also it looks like the issue already has a pull request waiting to solve it.
sass/sass#713
Sass should be fine with mixing syntaxes. We do it at work and it compiles nicely.
If your desire is to layer your styles on top of bootstrap you might want to leave boostrap as is and just create a "bootstrap-overrides.sass" file with your modifications. This might be the simplest way to use bootstrap and keep it updated as improvements are released.
If you really want to fork the project I'm afraid you are probably on your own. At least until sass-convert is updated.
--John
On May 27, 2013, at 3:28 PM, Ryan Burnette notifications@github.com wrote:
I think sass-convert is its own thing. I'm going to see if I can submit an issue about it specifically.
I thought the Sass compiler would freak out if I gave it a mix of files in both syntaxes. The last time I tried that it didn't appear capable of handling such. So I tried to convert over to all Sass syntax for that reason. I'll revisit the prospect of having a project mixed across the two syntaxes.
The core motivation is that I want to write in Sass instead of Scss on my next project.
—
Reply to this email directly or view it on GitHub.
Thanks, @jlong, for the quick response. This only appeared to be an issue to me based on my misunderstanding that mixing syntaxes would break the compiler. I asked this question to an expert at a conference and was told it wasn't possible. That was a couple years ago. I suspect that the answer was as wrong then as it is now. ;) I just tested and it's working great.
I always make a bootstrap/ and bootstrap-modified/ folder in addition to my own project/ folder so I can quickly update the core on all my projects.
I'll also take this opportunity to say how much I appreciate this project. I literally use it every day. I really love Bootstrap. Being a Sass user, however, I would have never adopted it without you and the other contributors' help. I hope one day I can pay it back or contribute to the project.
Glad that you found a good solution!
@jlong Apparently the problem I had was just a problem with the Sass syntax highlighting I'm using in Sublime Text 2. :(