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

Describe the bug

As you see , there is one more "\n"

How to reproduce

let a = (cat test.txt)
2. echo $a
3. It will be one more "\n"

Expected behavior

No '\n'

Screenshots

![unknown2](https://user-images.githubusercontent.com/60290

Sanity checks

• My issue relates to a specific CLI completion spec (e.g. git checkout is missing options in git completion spec). If your issue is more general, please create your issue here: withfig/fig
• I have searched [github.com/withfig/autocomplete/issues](https://gi

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

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

It is possible to write a loop using a different syntax like:

while (( i++ < 10 )) { echo i is $i } 

Issue:

The syntax highlighting fails on the { echo i is $i } part. Has this been a conscious decision made in the past? If not is it possible to fix this?

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