J. Voigt

The marked module makes it relatively easy to extract out code blocks. ``` coffeescript codeFrom = (source) -> (t.text for t in marked.lexer(source) when t.type == 'code').join "\n" ``` Demo...

@FiloSottile wrote: "Would it be possible to offer an option for plain code output? Like --code, that by default creates the corresponding .py, if specified in a folder?" @jashkenas replied:...

@Truffula: Alternatively, you could just use a simple bash function for this: ``` # Extract indented code blocks literature () { grep '^ ' $1 | sed 's/^ //' }...

Good point re sub-sub-lists. The following is probably safer, though still not going to handle every edge case: ``` bash # Extract indented code blocks literature () { grep '^...

@xiongchiamiov In lieu of a RESTful API, one can replicate the backend (`mongorestore dump/explainshell`) and hack up a little CLI interface. FWIW, [here's an elementary proof-of-concept](https://gist.github.com/joyrexus/8025934). The `classification` collection could...

FWIW, the [README](https://github.com/joyrexus/buckets#buckets) now provides a quick overview.

@maxogden's [dat](https://github.com/maxogden/dat) project looks very promising.

@jbenet wrote: > I will be building the equivalent data package registry tool once we converge on a standard Note also existing tooling such as [dpm](https://github.com/okfn/dpm) and [datapackage-json](https://github.com/maxogden/datapackage-json#datapackage-json). Sidenote: curious...

@arfon wrote: > I'd love to hear your thoughts on the idea of using JSON-LD as a lightweight metadata format for describing scientific software. Curious if you're targeting standalone scientific...

I have the same need. In our case, we're processing [events with multiple event types sent on a single kafka topic](https://www.confluent.io/blog/put-several-event-types-kafka-topic/). In other words, we're receiving events on a given...