Various configs I personally use in my dev environments.
| Plugin | Description |
|---|---|
goolord/alpha-nvim |
Welcome dashboard |
catppuccin/nvim |
Color scheme (Disabled) |
nvim-lualine/lualine.nvim |
Status bar |
nvim-neo-tree/neo-tree.nvim |
Directory tree side bar, opened files side bar |
hrsh7th/nvim-cmp |
Autocomplete |
folke/persistence.nvim |
Sessions persistence |
nvim-lua/plenary.nvim |
Async utils (required by other plugins) |
nvim-telescope/telescope.nvim |
Explorer utils (grep, find file) |
folke/tokyonight.nvim |
Color scheme (Enabled) |
nvim-treesitter/nvim-treesitter |
Syntax tree parser |
nickjvandyke/opencode.nvim |
OpenCode AI assistant integration |
- cpp
- cmake
- lua
- rust
Some configs can be set through overriding default env variable values.
Nvim will try to load env variables for the session from <CWD>/.nvim/.env
| Env variable | Default Value | Description |
|---|---|---|
NVIM_CLANGD_BUILD_DIR |
build |
A directory where clangd will search for compile_commands.json |
NVIM_CLANGD_CPP_STANDARD |
-std=c++23 |
Cpp standard for clangd |
$ git clone <repo>
$ cd ~/.config
$ ln -s <repo_root>/nvim nvim # Create a sym link to configGeneral example opencode.json config with default permissions.
Custom definition for tokyonight-moon color scheme.
tui.json config with tokyonight-moon as default color scheme.
Copy necessary configs into ~/.config/opencode.
Note that some configs might require manual update based on environment (e.g. providers).