Shell

• 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

Related problem

In nushell/nushell#3717 Nushell has been made available for installation via winget on Windows. In nushell/vscode-nushell-lang#39 has been made available from the shell picker in VS Code.

The final feature missing for turn-key setup on Windows is making Nushell available on [Windows Terminal](https://www.microsoft.com/en-us/

The problem

Users installing Spaceship via homebrew don't know they have to add following lines to their .zshrc:

autoload -U promptinit; promptinit
prompt spaceship

Describe the solution you'd like

Homebrew has to report a caveat with this information. Here's an example how they do that with nvm formula: https://github.com/Homebrew/homebrew-core/blob/23f6654873c

Installed using the "Using packages" install how-to section for Ubuntu, but syntax highlighting does not work. .zshrc file obviously does not have sourcing information, and after trying all of the "source" lines from the INSTALL.md, it still doesn't work. clearly zsh-syntax-highlighting is installed somewhere different than the git installations, and those source lines won't work for the Ubuntu re

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

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

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