Charlie Robbins

@jamesls if an ambitious contributor were to want to implement this, how might you suggest they approach adding this feature? For example: would a limited implementation of say `@app.batch_job()` that...

The only reason I would want this feature is for using `nexpect` with `procstreams`, but the solution isn't turning out as elegant as I would like. Maybe the solution here...

@maryrosecook Great. To my other point: I'd be happy to help with a lexer / parser implementation in Javascript. I really think there could be some very engaging ways to...

Personally I agree with @maryrosecook > Isla is not that complicated, so its compiler doesn't need to > be written in a heavy duty language. Given the limited number of...

@maryrosecook Nice! I'll take a stab at the lexer this weekend. Should I fork? Or just create an `isla.js` repository? This is your call, `isla.js` makes sense only if the...

@maryrosecook Pretty much done with the Javascript lexer. 1. Fully-parsed lexemes [are here](https://github.com/indexzero/isla.js/blob/master/test/fixtures/lexemes.js) 2. From [these fixtures](https://github.com/indexzero/isla.js/tree/master/test/fixtures/isla) Next up is parsing. The sample syntax in `hallway.is` suggests that `items` is...

@maryrosecook Got it. But shouldn't the `hallway.is` script throw for an undefined type `room`? It is not defined in that script. Or is `room` a built-in type?

This is a really neat idea! The world of `webpack.config.js` and other JavaScript config files has become much larger since this project was written. Evaluating JavaScript even in a new...

API thoughts ``` js require('nconf') .dir('./dir/of/config/files'); ```

WIP in `gh-18` branch