feat: launch REPL as own shell

[sockmaster27]

Fixes #372

[sockmaster27]

Sorry for the large diff.
This change required modifications to many of the dead handlers, and I thought it might finally be time to kill them, rather than make more untestable changes.

[magnus-madsen]

Sorry for the large diff. This change required modifications to many of the dead handlers, and I thought it might finally be time to kill them, rather than make more untestable changes.

OK. I take a look.

[magnus-madsen]

How can it work without shell quote?
Does VSCode escape weird path names?

Can you try to create an absurd path and open it in VSCode? (E.g. a path with lots of spaces and special chars and quotes)

[sockmaster27]

This happens when Ctrl+C is pressed

[sockmaster27]

How can it work without shell quote? Does VSCode escape weird path names?

Can you try to create an absurd path and open it in VSCode? (E.g. a path with lots of spaces and special chars and quotes)

This is as strange as Windows is allowing me to go and it works just fine:

[magnus-madsen]

What happens if you:

• click Run Main
• ctrl + c
• click Run Main?

Does it open a new terminal as hoped?

[magnus-madsen]

How can it work without shell quote? Does VSCode escape weird path names?
Can you try to create an absurd path and open it in VSCode? (E.g. a path with lots of spaces and special chars and quotes)

This is as strange as Windows is allowing me to go and it works just fine:

Okay. Wow. I guess maybe it is escaped?

[magnus-madsen]

Where does the exit code -107... come from?

I assume if you type :exit in the repl something else happens?

[sockmaster27]

Okay. Wow. I guess maybe it is escaped?

My guess would be that it isn't necessary if the process is started directly without going through a shell:
https://nodejs.org/api/child_process.html#child_processspawncommand-args-options

[sockmaster27]

What happens if you:

* click `Run Main`

* ctrl + c

* click `Run Main`?

Does it open a new terminal as hoped?

Yes

[magnus-madsen]

What happens if you:

* click `Run Main`

* ctrl + c

* click `Run Main`?

Does it open a new terminal as hoped?

Yes

Ok, so it would seem that "it works well"?

[magnus-madsen]

In addition, can you try two things:

• What happens if the Flix program terminates with an error (try main with ???)
• What happens if the Flix program calls System.exit (you will need import static ...`)
• What happens if the Flix program loops (you can just write a tail recursive function that calls itself).

[sockmaster27]

Where does the exit code -107... come from?

I assume if you type :exit in the repl something else happens?

That exit code seems to be mean that the process has been 'forced' to quit via Ctrl+C.
Quitting it normally is equivalent to just closing it.

[magnus-madsen]

But what happens with :exit? is it different from ctrl+c is my question

[sockmaster27]

In addition, can you try two things:

* What happens if the Flix program terminates with an error (try main with `???`)

* What happens if the Flix program calls `System.exit` (you will need import static ...`)

* What happens if the Flix program loops (you can just write a tail recursive function that calls itself).

• The error is correctly reported in the shell and it continues to live on.
• Unfortunately, exits the terminal:
  
• Terminal becomes unresponsive until killed via Ctrl+C or the trash icon.

[sockmaster27]

But what happens with :exit? is it different from ctrl+c is my question

It just quits the shell gracefully and hides the panel.

[sockmaster27]

Ok, so it would seem that "it works well"?

Other than the ugly error reporting, yes.