Error when processing files with CR/LF (Windows) line endings about vash HOT 3 CLOSED

Vash's lexer attempts to normalize the endings to \n (https://github.com/kirbysayshi/vash/blob/master/src/vlexer.js#L167).

Is there a place I can see this bug in action?

I can't reproduce it with current vash: http://requirebin.com/?gist=kirbysayshi/9622558.

I'm not too familiar with docpad. Do you know what version of Vash it's using?

from vash.

I tried to recreate the problem in a small project on another pc, but it works fine and I couldn't reproduce the error no matter what file encoding or line ending I selected. Maybe the other project was using an older version of vash, I'll check that tomorrow. If there ever was a problem, it's fixed now.

from vash.

Definitely let me know if you do discover what the issue was. I recently
fixed Vash to strip the BOM from a file, perhaps that was causing issues.

Yip yip,
~ Drew*

On Wed, Mar 19, 2014 at 5:35 PM, Maarten88 [email protected] wrote:

Closed #33 #33.

Reply to this email directly or view it on GitHubhttps://github.com//issues/33
.

from vash.