Update README.md

Several people have asked why the bindings weren't setup after installing via their package manager

I imagine they skip straight to the install section with the name of their pkg tool, without reading the rest of the documentation.

This should hopefully make that a bit more clear! Albeit while introducing more repetition
This commit is contained in:
Ellie Huxtable 2022-05-19 23:34:29 +01:00 committed by GitHub
parent cd2a3ab7d5
commit 4096c6ee8c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -132,12 +132,16 @@ toolchain, then you can run:
cargo install atuin cargo install atuin
``` ```
And then follow [the shell setup](#shell-plugin)
### Homebrew ### Homebrew
``` ```
brew install atuin brew install atuin
``` ```
And then follow [the shell setup](#shell-plugin)
### MacPorts ### MacPorts
Atuin is also available in [MacPorts](https://ports.macports.org/port/atuin/) Atuin is also available in [MacPorts](https://ports.macports.org/port/atuin/)
@ -146,6 +150,8 @@ Atuin is also available in [MacPorts](https://ports.macports.org/port/atuin/)
sudo port install atuin sudo port install atuin
``` ```
And then follow [the shell setup](#shell-plugin)
### Pacman ### Pacman
Atuin is available in the Arch Linux [community repository](https://archlinux.org/packages/community/x86_64/atuin/): Atuin is available in the Arch Linux [community repository](https://archlinux.org/packages/community/x86_64/atuin/):
@ -154,6 +160,8 @@ Atuin is available in the Arch Linux [community repository](https://archlinux.or
pacman -S atuin pacman -S atuin
``` ```
And then follow [the shell setup](#shell-plugin)
### From source ### From source
``` ```
@ -162,6 +170,8 @@ cd atuin
cargo install --path . cargo install --path .
``` ```
And then follow [the shell setup](#shell-plugin)
## Shell plugin ## Shell plugin
Once the binary is installed, the shell plugin requires installing. If you use Once the binary is installed, the shell plugin requires installing. If you use