b9a3e0650a
The search for an empty line incorrectly does +1 which happens to be skipping a `\n`, but in case of windows line endings it skips the `\r` but sees a `\n` afterwards and incorrectly assumes that it is a empty line. This doesn't change the behavior of doing +1 when there's not a line ending. Making it correct actually triggers a bunch of changes, where half of them are better and half of them regressions. So I'm going to send another pull request to fix that case. |
||
|---|---|---|
| .. | ||
| __snapshots__ | ||
| jsfmt.spec.js | ||
| windows.js | ||