How do I set up…
What is…
barebone Neovim setup?
This barebones Neovim setup has:
- lazy.nim plugin manager
- structured
plugins/directory setup - color scheme
- nvim-tree plugin (for demo on how to install a plugin)
Step 1: lazy.nim
Follow the installation guide, using the Structured Setup and set up your plugins/ folder following Usage > Structuring Your Plugins.
Your directory should look like the following:
/Users/ashliew/.config/nvim
├── init.lua
├── lazy-lock.json
├── lua
│ ├── brainuser5705
│ │ ├── lazy.lua
│ │ └── settings.lua
│ └── plugins // each file in this directory is for a plugin
│ ├── devicons.lua
│ ├── init.lua
│ ├── tree.lua
│ └── treesitter.lua
└── README.md
Step 3: nvim-tree
Add the plugin module to plugins/.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
return {
{
"nvim-tree/nvim-tree.lua",
version = "*",
lazy = false,
dependencies = {
"nvim-tree/nvim-web-devicons",
},
config = function ()
require("nvim-tree").setup({
sort = {
sorter = "case_sensitive"
}
})
end
}
}
This step requires a Nerd Font in order to properly display icons. See Nerd Font.
a Nerdfont for Terminal?
Nerdfonts are often required for several Neovim plugins for proper display of icons.
- Download a Nerd Fonts on your system.
- Alternatively, you can download all the fonts with
brew install font-hack-nerd-font
- Alternatively, you can download all the fonts with
- Click on the downloaded font file to install it.
- Go to Terminal > Settings > Profiles > Font and select a Nerd Font.
the difference between terminal, shell and console?
Whilst ricing, you might come across these terms…“make zsh your shell”, “use iTerm as your terminal/terminal emulator”… but what is the difference?
Here’s how I see it:
- Shell: the actual interpreter of your commands that you put into the terminal
- Terminal: software (these days) that takes input and displays output for the shell
- Terminal Emulator: same thing as a terminal, emulator meaning software since historically terminals were physical devices
- Console: a physical/virtual device that’s connected to the computer at a low level (kernet, bios, system messages)
