Nathan Lilienthal

See https://github.com/nixpulvis/oursh/issues/5#issuecomment-431593744, specifically note, we only need to built these functions for this initial issue. - `complete_command` - `complete_builtin` - `complete_executable` - `complete_path` (includes ~, and globs)

This is currently waiting for a `Job` interface for piping, so we can just call `left.run_piped(...)` or something like that.

First pass implementation merged in #51.

This was implemented like this to actually make use of the systems `#!` functionality, however there's no real reason we can't create a `Job` with the correct executable path, and...

2.13.3 Patterns Used for Filename Expansion in https://pubs.opengroup.org/onlinepubs/9699919799/

I've started work on the LALRPOP implementation. Even if we decide on conch for the POSIX grammar I believe this will be a good choice for the modern grammar.

This will be pretty finalized as I figure out the custom lexer for LALRPOP.

#22 will inform most of the open questions here.

Currently the structure returned by a `parse` can be any kind of `Program`, but the `Program` trait doesn't expose the complete AST. We need some form of AST to assist...

https://github.com/zsh-users/zsh-syntax-highlighting/tree/master/highlighters