Multiline strings with backslashes are silently truncated

[anlutro]

I have helpers like this in some of my code. These used to work fine, but are now silently truncated (no errors) so that anything after the slash and newline isn't included as part of the variable.

$media-medium: "screen and (min-width: #{$break-medium-min}) \
and (max-width: #{$break-medium-max})";

I can provide a sass-spec PR a bit later.

[anlutro]

Oddly enough, the above now works when I remove the \ - maybe this is intentional? I actually prefer it without the \, but I still feel that it should be allowed - if it's not too much work to implement.

[mgreter]

Libsass now much more correctly parses escaped chars. Maybe ruby sass has a special rule for lines with trailing backslashes, which I probably didn't encounter when I did the refactoring. Anyway, seems easy enough to support. But in term of CSS the backslash there does not make much sense IMO!

[anlutro]

sass/sass#1237 may be of interest regarding the backslash. It was my understanding that backslashes to denote multiline strings was valid CSS and should therefore be valid Sass/SCSS.

[xzyfer]

Spec added sass/sass-spec#278

[am11]

I can reproduce this issue with current master.
In other words, sass/sass-spec#278 is failing.

[mgreter]

Unfortunately I, Travis-CI and Appveyor cannot reproduce the issue.
@am11 I'm going to close this since we have this CI tested!
Please open a new issue with your output if problem persists!
P.s. I'm also always testing specs with perl-libsass on windows 😉

[am11]

@mgreter, this only happens when git is configured to auto-correct endings. Lets say you type/paste the following in notepad:

$media-medium: "screen and (min-width: #{$break-medium-min}) \
and (max-width: #{$break-medium-max})";

(or the spec code)

notepad will surely add \r\n. 😎

[mgreter]

Can you open a new issue for that with expected and actual output! Thanks!

[am11]

@mgreter done #1067. :)

[xzyfer]

There used to be a couple specs dealing with windows line ending but I fear that may have broken since we've auto generated the specs a couple times recently.