• Dynamic variable naming.
• Internal variables.
• Turn the non-functions into functions.
  • This is so tests can be written.
  • It also shows a working use case for the task.
• Add a CONTRIBUTING.md.
• Look into side effects of using shopt and set.
• /dev/tcp
• Convert to pdf
  • Add a cover.
  • Add references.
• Write some

Current behavior

Expected behavior

Relevant Zsh configuration (.zshrc)

Irrelevant with the issue

Environment

Spaceship version: `3.11

Solaris and Illumos use Bash as the default shell. However, currently bash-it does not work as expected on them.

This can be fixed as described, tested, and confirmed here.

Here's what I suggest:

• In install.sh, check for `$0S

• https://openports.se/shells/zsh-syntax-highlighting
• http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/shells/zsh-syntax-highlighting/
• Might as well link to https://repology.org/project/zsh-syntax-highlighting/versions so people can quickly check whether their distro's covered or not

Kudos to Matthew for making the former happen in the first place :-)

Steps to reproduce

Run asdf. In help output a line is printed for the asdf env command:

asdf env <command> [executable]      Prints or runs an executable under a command environment

I would assume <command> is an arbitrary command. But from what I can tell needs to be a plugin name or a shim name? I'm also not sure how this differs from executing the shim directly.

FY

The current instructions: README.md#oh-my-zsh, suggest to add zsh-completions to plugins and rerun compinit.

But that's sub-optimal. This will cause Zsh to rebuild the completion cache twice on each Zsh invocation: The first when you source oh-my-zsh, and the second time whe