• 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

After using Bash-it very happily on Linux, I'm now trying it on macOS (10.15.5, with bash 3.2.57), and I'm having all sorts of weird line break/line wrap problems. The problems seem to stem from scm_prompt_info, as they don't appear when I'm using a theme that doesn't use it or when I'm not in a git repo.

The problems I'm seeing include unexpected line breaks in the middle of my prompt, early

• 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 :-)

Thanks a ton for any helpful feedback

I need help with getting best quality GIFs.

I am not used to CSS syntax so it would be amazing if you add a lot of example config.yml files. Also, try adding config.yml files for the GIFs you are displaying in your README.md. They look fantastic. I have spent hours trying to get perfect GIF but no luck.

I don't know what value to give for shadow

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

Is your feature request related to a problem? Please describe.
yes, when i source a script file, i'd like to be able to tell if it really sourced. i ran into a problem where i was sourcing a file but it really wasn't getting sourced because i was in the wrong directory.

Describe the solution you'd like
maybe something like scope_show --aliases and scope_show --commands and `scop