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

@ -131,6 +131,8 @@ toolchain, then you can run:
``` ```
cargo install atuin cargo install atuin
``` ```
And then follow [the shell setup](#shell-plugin)
### Homebrew ### Homebrew
@ -138,6 +140,8 @@ cargo install atuin
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/)
@ -145,6 +149,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
@ -153,6 +159,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
@ -161,6 +169,8 @@ git clone https://github.com/ellie/atuin.git
cd atuin cd atuin
cargo install --path . cargo install --path .
``` ```
And then follow [the shell setup](#shell-plugin)
## Shell plugin ## Shell plugin