https://rosettea.github.io/Hilbish/docs/Recent content in Introduction on HilbishHugo -- gohugo.ioen-ushttps://rosettea.github.io/Hilbish/docs/faq/Mon, 01 Jan 0001 00:00:00 +0000https://rosettea.github.io/Hilbish/docs/faq/Is Hilbish POSIX compliant? No, it is not. POSIX compliance is a non-goal. Perhaps in the future, someone would be able to write a native plugin to support shell scripting (which would be against it’s main goal, but ….) Windows Support? It compiles for Windows (CI ensures it does), but otherwise it is not directly supported. If you’d like to improve this situation, checkout the discussion . Where is the API documentation?https://rosettea.github.io/Hilbish/docs/getting-started/Mon, 01 Jan 0001 00:00:00 +0000https://rosettea.github.io/Hilbish/docs/getting-started/To start Hilbish, open a terminal. If Hilbish has been installed and is not the default shell, you can simply run hilbish to start it. This will launch a normal interactive session. To exit, you can either run the exit command or hit Ctrl+D. Setting as Default Login shell There are a few ways to make Hilbish your default shell. A simple way is to make it your user/login shell.https://rosettea.github.io/Hilbish/docs/opts/Fri, 14 Apr 2023 01:01:10 -0400https://rosettea.github.io/Hilbish/docs/opts/Opts are simple settings and switches to control certain Hilbish behavior. This ranges from things like the greeting messages on bootup to “autocd” functionality. They can be changed via a simple assign (like hilbish.opts.namehere = true). Available Opts autocd The autocd opt (default false) makes it so that if a lone path is ran, Hilbish will change directory to that path. Example: sammy ~ ∆ hilbish.opts.autocd = true sammy ~ ∆ ~/Downloads sammy ~/Downloads ∆ history This opt controls if Hilbish will store commands in history.