Multiline strings with backslashes are silently truncated (CRLF/Windows version)

[am11]

Related to #942.

Given the following input:

$v: ".foo \
.bar";

#{$v} {
    color: #F00;
}

div {
    content: "foo\
bar";
}

The output is:

.foo.bar {\n color: #F00; }\n\ndiv {\n content: "fobar"; }\n

if and only if the CRLF linefeeds were used in the input.

Further notes:

Using node-sass master:

:: this is cmd
mkdir \temp
notepad c:\temp\blah.scss :: type the aforementioned Sass code, save and close notepad
cd path\to\node-sass\cloned\directory
node

require('./').renderSync({file:'c:/temp/blah.scss'}).css.toString()

outputs:

'.foo.bar {\n  color: #F00; }\n\ndiv {\n  content: "fobar"; }\n'

Ctrl+C to exit node.js REPL.

Run:

:: assuming you have mingw in your path
dos2unix c:/temp/blah.scss
:: dos2unix utility replaces \r\n with \n
:: dos2unix utility is reciprocal of unix2dos utility
node

require('./').renderSync({file:'c:/temp/blah.scss'}).css.toString()

outputs:

'.foo.bar {\n  color: #F00; }\n\ndiv {\n  content: "foobar"; }\n'  //expected output 
                                                                   // (the 'o' in foobar is not
                                                                   //  missing anymore)

[mgreter]

First part would have been enough 😉 Once I knew what to look for it was a pretty easy fix.
Probably took less time to fix it (#1066) than to write this.
Now I'll have a 🍺 and checkout the sourcemap issues.

[am11]

👍
Good idea; and I will go out and get some fresh oxygen 🚬 😸

On this note, should we configure appveyor to clone sass-spec repo with CRLF ending to test Windows environment verbatim?

[mgreter]

I like and fear that idea 😈 On this account I think I still have not enabled windows linefeeds on windows by default. Would be a good time to actually try it out. Although I'm not sure if the spec runner really is that picky about lineending types currently.