As the Neovim's version of this colorscheme is written in Lua and
doesn't work on Vim, this version of the theme is added to achieve
almost the same look/experience in both editors.
This colorscheme implements the vim-airline version of the theme, that
is also used in Neovim (the airline plugin) and needs of this to look
integrated.
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.
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.
This is yet another nvim completion plugin that got deprecated and
archived, due to the lack of maintainers, by its' author. Therefore the
submodule is being deleted from this repo.
nvim-compe was deprecated by it's original author leaving explicit
instructions that their work was continuing on plugin nvim-cmp.
Therefore in order to use this new version, nvim-compe is being deleted
in favor of nvim-cmp and its' extending plugins (cmp-nvim-lsp,
cmp-buffer, cmp-path)
This other Onedark colorscheme adds some functionality regarding
highlighting with Treesitter information and corrects some issues with
Neovim's LSP diagnostics formatting.
Stop versioning sub-modules that are really Vim/Neovim plugins. The use
of Git sub-modules for such projects has the only purpose of not
using/installing a plugin manager for Vim/Neovim, therefore, as while
using a plugin manager there's no versioning of those plugins, there is
no real need for such functionality with Git either.
Since Neovim packages are used in the repository as Git submodules to
avoid using an external package manager, there is no need to track those
submodules' history. Therefore, using those submodules as shallow
repositories has the same behavior as if a package manager unpacks their
latest version on the corresponding directory.
Since Neovim/Vim packages are used in the repository as Git submodules
to avoid using an external package manager, there is no need to track
those submodules' history. Therefore, using those submodules as shallow
repositories has the same behavior as if a package manager unpacks their
latest version on the corresponding directory.
Added a second autocompletion plugin for trying with Neovim's native LSP
to compare performances and provided results (Completions, Definitions,
Hover, References, Signature Help, and Symbols) between completion-nvim
and this one, nvim-compe
Neovim's LSP doesn't have automatic completions, only completions
manually invoking omnifunc through i_CTRL-X_CTRL-O. Adding this helping
module Neovim can have automatic completions for its LSP.