cmark/js/markdown, branch master My own fork of cmark for commonmark conversion Use browserify to make js code more modular. 2014-10-18T23:39:33+00:00 John MacFarlane jgm@berkeley.edu 2014-10-18T23:16:49+00:00 fb143fbc1705bb4d59b5d4ebbb5454866cf1b76c * Moved js library code to `js/lib`. * `js/stmd.js` is now generated from these files using browserify. * Factored out `html5-entities.js` and `from-code-point.js` from main js parsing code (which is now `index.js`). * Moved `js/markdown` to `js/bin`. 
* Moved js library code to `js/lib`.
* `js/stmd.js` is now generated from these files using browserify.
* Factored out `html5-entities.js` and `from-code-point.js` from main
  js parsing code (which is now `index.js`).
* Moved `js/markdown` to `js/bin`.
Fix the output of the JS `markdown` executable. 2014-09-04T22:47:45+00:00 yamadapc tacla.yamada@gmail.com 2014-09-04T22:47:45+00:00 4d9b2de5f87bb1dad1a9a061d87f62b332a45dc4 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. 
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.
Initial commit 2014-08-14T05:56:32+00:00 John MacFarlane jgm@berkeley.edu 2014-07-22T05:29:16+00:00 870e63be7360b5a0097a27656048e853bc720464