Irakli Gozalishvili

I thought I'd post here as it was mentioned in the other [discussion thread I was involved with](https://gist.github.com/rtfeldman/5f015adbdfbba541c7e7e1409b6efeef#gistcomment-1832260) I believe the problem observed in the examples is with a selection...

> @Gozala Can you share your solution for tracking selection in model? @rofrol I did describe it in the mentioned thread. As of project I mentioned, it is unfortunately not...

I believe ideas is that spread operator will handle that: ``` js const b = #{ ...a, z: 3, t: 4}; ```

Alternatively it could be similar to how numer literals were extended: ``` js set#[1, 2, 3] ``` or ``` js #set[1, 2, 3] ```

@AgentME well the problem is that multiple web socket servers are started with the same port and the second one obviously fails. I do not see how `--url` or `--port`...

This is blocked by rogerwang/node-webkit#61

This is blocked by rogerwang/node-webkit#61

This is blocked by rogerwang/node-webkit#91

I've briefly looked into and it seems like error is coming from flow itself, more specifically here is some of my observations: I set a breakpoint on the above mentioned...

Ok so I have tried changing following line https://github.com/lukehoban/atom-ide-flow/blob/master/lib/util-flow-command.coffee#L79 to: ``` args: ['type-at-pos', fileName, bufferPt.row + 1, bufferPt.column + 1, '--json'] ``` Which does not seem to resolve it. From...