Guillaume Knispel

I'm a little busy, I'll probably take a look this WE.

One problem is that Win32 escaping/splitting of the command line is not 100% standardized. But I guess by default we could use the MSVC / CommandLineToArgvW way and add an...

Update: when we go through cmd.exe we must also take into account its own parsing rules to do proper escaping.

This is slightly more tricky than it looks like at first, for example for now with no quoting/escaping at all: ``` $ wcmd "foo&bar" 2000 'foo' n’est pas reconnu en...

A problem with never quoting/escaping the first param at all is also that e.g. `wcmd "c:\Program Files (x86)\Notepad++\notepad++.exe" bla.txt` would not work, while oddly `wcmd echo toto \& "c:\Program Files...

But then you can't have your filenames you want to edit escaped, and the double escaping just for the (first) program is nasty. Actually I did a mistake `wcmd echo...

So for now I more in favor of the general idea of quoting and escaping everything if needed, and nothing if doing for example: wcmd --raw 'notepad&pause', but I'll still...

> The first parameter of start is ["title"] Yes, only with quotes though, and most of the time useless anyway; except when launching a command line program that does not...

@HeathNaylor yep, I thought about that precisely when trying tmux :)

I think an extra background outbash.exe should be automatically started by the first interactive one, and somehow kept running _at least_ until WSL is shut down (not only all interactive...