Looking at https://github.com/neovim/neovim/releases/. I know I can just brew install..
, and that's what I normally do (and will probably do after writing this up). But I feel like as a developer I should be comfortable installing a program (and I'm mostly curious). So the directory structure consists of bin
, lib
, and share
:
.
├── bin
│ └── nvim
├── lib
│ └── nvim
│ └── parser
└── share
├── locale
│ ├── af
│ ├── ca
│ ├── cs
│ ├── cs.cp1250
│ ├── da
│ ├── de
│ ├── en_GB
│ ├── eo
│ ├── es
│ ├── fi
│ ├── fr
│ ├── ga
│ ├── it
│ ├── ja
│ ├── ja.euc-jp
│ ├── ko.UTF-8
│ ├── nb
│ ├── nl
│ ├── no
│ ├── pl.UTF-8
│ ├── pt_BR
│ ├── ru
│ ├── sk
│ ├── sk.cp1250
│ ├── sv
│ ├── tr
│ ├── uk
│ ├── vi
│ ├── zh_CN.UTF-8
│ └── zh_TW.UTF-8
├── man
│ └── man1
└── nvim
bin
: I'm assuming I can just move bin/nvim to /usr/local/bin or /opt/somewhere? Is that usually all that's done?lib
: What's the point of this directory if I don't need it anymore? In general, how would one know if the binary they'remv
'ing to theirPATH
needs dynamic libraries?share
: looks like a lot of useful stuff in here like man pages, which I can probably manually install, and a bunch of important neovim files.