Eero Helenius

Thanks for the quick reply! I will give negative lookaheads a go. Regarding character ranges, I've already translated them into regexps, although I'm not quite sure whether I've got the...

@aengelberg: Many thanks for the suggestions! Your version of `Char` works great, and I can use the information you provided to fix the other rules, too. I haven't yet quite...

Left a couple of minor comments, but 👍 👍 & 🥇 for putting generated files outside the installation directory.

@jelovirt that sounds good to me. Alternatively (or additionally), you could maybe pass a property file as a command-line argument to `dita`. I guess even with the way things currently...

Hmm, yeah, looks like it. I don't remember why I never created the PR, I'm afraid. I can certainly make the PR if necessary, but the fix is so small...

>I'm assuming the bug you discovered is a result of the introduction of streamed value responses, as originally the `done` on successful `eval` was part of the only `value` response...

For Markdown, guess one option would be to write a [CommonMark Visitor](https://github.com/atlassian/commonmark-java#use-a-visitor-to-process-parsed-nodes) to extract the headings from the Markdown files and include them in the doc tree.

Implementing this properly would require improvements to the syntax definitions. Specifically, `bar` in the example above should have a scope like `meta.namespace-alias.clojure` to distinguish it from from a var in...

This is a bit tricky because while things like functions and keywords are things the ClojureScript compiler knows about, specs are not. Tutkain currently has no infrastructure for looking up...

A related idea: make the backchannel optional. This would make e.g. connecting over an SSH tunnel or connecting to production runtimes more straightforward.