This is my personal neovim config.
When using cmake, neovim requires a compile_commands.json
file
present in the ./build
directory of the project.
This ensures, that all dependent header files are found.
To generate a compile_commands.json
it is necessary to run
cmake with the -DCMAKE_EXPORT_COMPILE_COMMANDS=ON
parameter.
A build workflow could look like this:
mkdir -p build && cd build
cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=ON ..
make
This produces the compile_commands.json
in the ./build
directory,
which neovim expects.
Go development works out of the box.
To be able to install all required Mason packages, luarocks is required.
For debugging to work, debugpy
must be installed using mason.
Mason installations are done automatically.
If a virtual environment is used, it is required to install debugpy
manually within it:
source .venv/bin/activate
pip install debugpy
When adding a virtual environment, neovim has to be restarted to ensure that it is being used.