> Very interesting! Do you transmit this metadata on a different fd, like 3?
At the moment there is POC code to transmit over fd 3 but I’m looking into using UNIX sockets instead.
> Super cool. Since it's Go, does that mean runtime errors will silently fail and keep chugging along? /dig ;)
This project predates Rust 1.0 so it was a no brainier at the time to use Go. But actually I do think Go is well suited for this type of problem because much as some complain about errors being regular types, the way Go encourages granular handling of errors rather than larger try / catch blocks or exceptions does lead to more tailored error messages. Which ultimately helps explain the problem better for the end user.
Not taking anything away from Rust or any other language. Nor am I saying Go’s error handling doesn’t have its problems. Just that I’d probably choose Go again if I were to start this project tomorrow.
> Can you customize the PS1?
Every part of the shell is customisable. However rather than having hard to discover environmental variables that can alter the shells behaviour, instead there is a command called config that allows you to inspect every option.
At the moment there is POC code to transmit over fd 3 but I’m looking into using UNIX sockets instead.
> Super cool. Since it's Go, does that mean runtime errors will silently fail and keep chugging along? /dig ;)
This project predates Rust 1.0 so it was a no brainier at the time to use Go. But actually I do think Go is well suited for this type of problem because much as some complain about errors being regular types, the way Go encourages granular handling of errors rather than larger try / catch blocks or exceptions does lead to more tailored error messages. Which ultimately helps explain the problem better for the end user.
Not taking anything away from Rust or any other language. Nor am I saying Go’s error handling doesn’t have its problems. Just that I’d probably choose Go again if I were to start this project tomorrow.
> Can you customize the PS1?
Every part of the shell is customisable. However rather than having hard to discover environmental variables that can alter the shells behaviour, instead there is a command called config that allows you to inspect every option.
https://murex.rocks/docs/commands/config.html