Set in both editors the VSCode theme Dark+ variant. Each editor uses a
plugin built specifically for it, because Neovim's is written in Lua and
Vim's doesn't provide TreeSitter support.
In order to be able to re-load/reset default settings in colorscheme
onedark, there is no longer a function (`onedark#extend_highlight`) to
re-apply colors, but instead that can be achieved by re-loading the
highlighting with the `syntax reset` command.
From Iosevka's v4.0.3 to v22.0.0 many of the character variants used for
customizing the font in Neovim-GTK has changed codes. With this patch
those codes where updated to their current values using as reference the
project's Github page.
Since the NerdFonts project now includes codicon glyphs in standard
releases, so there is no need to indicate users to download some RC
version of the fonts.
Due to a deprecation in the cmp-nvim-lsp project plugin, renaming the
method used to update de default capabilities; there has to be changed
in settings as well.
Now LSP servers can be installed via meson-lspconfig, allowing them to
reside in local Neovim directories and not forcing the user to know
which dependencies need to be installed for each language.
meson-lspconfig depends on core functionality provided directly by
meson, that's why the other submodule has been also added to the repo.
The CoC extension coc-python got unmaintained (and it's repo archived:
https://github.com/neoclide/coc-python). Therefore there is no need to
keep the corresponding settings either coc-settings.json file.
To normalize the content of the file with others in the project, that
hold unicode characters (nvim/init.vim, vim/vimrc,
vim/coc-settings.json, among them) converted all unicode escaped codes
in their glyph representation. This change also brings more readability
to the file in the way that symbols represent more than code numbers.
Migrated, following TeeJ_Dv's advice, the auto-command creation to a Lua
function. As this auto-command only cares for the on_attach Lua scope,
it seems correct to have this one defined as a Lua function instead of
the legacy Vimscript.
There is too many instructions specifically for the code editors
Neovim/Vim. Having their instructions in the main project README file
can confuse and overwhelm.
Most colorchemes get the wrong color for the python class-keyword. This
fix overrides the default and groups “class” to be highlighted with the
same color than function declarations.
There is a comment in the file referring an where the tip came from.
An argument to a Neovim's Lua function that used to live in global
scope, now needs to be declared as part of the function definition, and
passed accordingly.
Renamed Vim-script and Lua modules to separate the functions from, which
settings correspond to the client part and which to the server part of
the LSP protocol for either editor.
In order to be able to complete, navigate and lint code according to the
project's modules and dependencies, there is the need to use
python-lsp-server plugins installed in the same virtualenv the project
uses. Although the LSP plugin manager (python-lsp-server) is not
installed inside the project itself.
This settings detect the presence of those executables and adjusts their
paths to use the ones inside the virtualenv.
From version 0.5 to 0.6 some changes in Neovim's Lua API occurred, and
some settings had stopped working. These changes are made to ensure
shortcuts and some stuff continues working on newer versions of Neovim.
Legacy behaviour was not considered and hence this configs may no longer
work on older stable versions of Neovim.
From version 0.6, Neovim comes with support to Treesitter, which helps
on navigating code's AST and adds the ability to make language specific
decisions with plugins.