Håvard Wormdal Høiby

This issue is resolved by the new command argument parser, `workflow-parser-arguments` should be deprecated.

Any thoughts on how far we want to automate this @relekang, @haakondi ?

So how and where do we want to add this automation? Should it belong to the `workflow-wm-windows-python` package (i.e. to check for python and install `pywin32`) or should this belong...

The `create-workflow-home` module does not support initializing other than on linux with i3 :/. ## Workaround Manually set up the `.workflow` folder with a `config.js` file and a `package.json`. You...

@haakondi Is this accurate to what we did? Could you add version info like `node`, `npm` etc?

Support for multiple monitors are planned for `workflow`. This support will likely make the flow files able to specify which monitors the different applications should be placed on. Until this...

That could be a start in the mean time. So that it's not broken at least.

This is actually a simplified step in the direction (albeit not the exact same direction) that I want to take `workflow`. I believe this functionality is much easier to achieve...

Ah, sorry, I didn't realize what you actually meant with extra _tab_ in `iTerm`. So what if we do this with two flags. 1. `openInExistingWindow` - try to reuse an...