Nathan Lilienthal

https://users.rust-lang.org/t/prevent-program-from-exiting-on-child-sigint/7685/13

https://www.gnu.org/software/libc/manual/html_node/Data-Structures.html#Data-Structures https://www.gnu.org/software/libc/manual/html_node/Launching-Jobs.html#Launching-Jobs

The [` bash`](https://www.gnu.org/software/bash/manual/html_node/Bash-Builtins.html) list, and [POSIX](http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html).

We should parse the arguments with `docopt` for each `builtin`.

Is now the right time to just switch over to something like `structopt` or `clap` itself?

I want to move all stream processing out of `main.rs` and into the fancy new `repl` module. I believe [`BufReadDecoder`](https://docs.rs/utf-8/0.7.4/utf8/struct.BufReadDecoder.html) will be needed.

So here's an idea (does lalrpop support it?), we return a parse error on incomplete syntax, and that's the input to the function that drives highlighting, completion, history selection, etc....

The initial `sh` style completion feature will be simple and fast enough to run inline, but after that point a more robust asynchronous implementation is needed.

@dread-uo I've been so busy writing all this POSIX stuff I haven't thought much about it. I spent a good part of tonight working on making the raw terminal mode...

In order to support current and future needs for completion, here is a more complete design. - `complete` (combine the below functions) - `complete_command` - `complete_builtin` - `complete_function` - `complete_executable`...