| Age | Commit message (Collapse) | Author |
|---|
|
Resolve test.js line-ending sensitivity blocking running tests on Windows
|
|
|
|
|
|
Cleaned up a missing semicolons, unused variables, undeclared variables.
|
|
|
|
A few undeclared variables - no big deal there. One use of block_end_line where block.end_line was meant (I believe).
Also - query as to whether the new keyword is needed when calling InlineParser as the function returns an object, so we're not dealing with an instance of InlineParser (I haven't changed this, just a query).
|
|
Previously, because of `console.log` semantics, if you ran:
```
make test PROG=js/markdown
```
You'd get a couple of errors caused by `console.log` calls putting `\n`
line breaks where they shouldn't. This fixes that by using
`process.stdout.write` instead of `console.log`.
This isn't something really important, but it's nice for all the
provided executables to pass the test suite.
|
|
Don't count an escaped # at the end as a closing string of #s.
Closes #16.
|
|
|
|
|
|
|
|
|
|
|
