Adds support for treesitter syntax / grammars when editing files.
This is currently an experimental neovim feature but is (very) likely to
be merged into the upstream in one of the next releases.
This is a plugin for reporting '$/progress' status messages from neovim.
Realistically, only (some) LSP servers actually use this, but it
provides a clean, minimal method for understanding what an LSP is
working on at the minute.
`Server.Rust`, `Server.Lua` and `Server.Json` support it at a minimum,
from my personal testing
This plugin provides project (and user) local configuration files for
LSP settings, similiar to coc-settings files.
By default, it will search
- $HOME/.config/nlsp-settings/<language-server>.json
- <project-root>/.nlsp-settings/<language-server>.json
for configuration, automatically updating the language server with the
settings found within. These override any settings set within lua...
bare this in mind.
You may access the associated files via:
:LspSettings [local] <language>|buffer
This plugin provides the tools for initializing language servers, using
the builtin neovim LSP client. It provides the major low level glue for
actually starting and configuring a given language server; however it
**does not** ensure that the actual language server is present on the
system / in PATH.
That function is handled by mason / mason-lspconfig, which will prompt
the user to install the necessary server(s) upon calling
`lspconfig[$server].setup { ... }`.
We provide a default on_attach function the sets up some default key
maps for LSP related functionality, loading a user overridable map of
language servers and their associated setup objects or functions.
Note that "setting up" a language server is not the same as loading it,
which is a considerably more expensive operation. Hence, we make no
effort to lazily setup language servers.
These were selected as they seem generally useful in everyday usage of
neovim. Vim/Lua is obvious, Json and Yaml is generally useful for
config editing.
These objects provide a nice abstraction over the underlying
complexities of configuring language servers in native Neovim.
The idea is to allow users of the module to define Server/s that can
just be included somewhere and have them activate with fuss.
That said, we *do* want ways of configuring the underlying systems, and
this module provides two, one for direct consumers of this module
(Spec.setup), and one for users *of predefined Servers*, in the form of
Server.with/1.
This commit removes all vimpeccable (vimp) usage from the code base, as
it has been superseded by 'psoxizsh.key'.
In addition to simplifying the code, this also removes the annoying
spurious errors that would be generated when reloading configuration.
One thing to note: this commit also remove most of the LSP config we
have for coc.nvim. This is intentional, and will be corrected via a
future patchset utilizing the native neovim LSP client, as coc has
become annoying to maintain.
This commit adds a file that users can use to lookup available key binds
that are set.
The big benefit here is largely discoverability, as psoxizsh users no
longer are required to search thorough the entire code base looking for
binds.
That said, we *only* cover those explicitly set by psoxizsh, but
covering any created by plugins that may be used.
Still, this is a significant improvement compared to the previous
situation, and more importantly; prevents the situation from getting
worse as we add more plugins.
NOTE: Must go through prior work (util/keymap, vimp) and codebase, to properly
search and replace all instances of key binding
This commit adds wrapper objects around vim.keymap functionality.
Bind represents a single key bind, which can be register/2'ed with
Neovim. By default, Bind enables noremap and silent (:h map-arguments)
by default, as this is almost always what a user wants.
BindGroup(s) are DAG collections of child BindGroup(s) inner nodes
and Bind leaf nodes. Options are passed down the tree, though they
may be overridden by child objects.
Together they allow callers to create composable, lazy key bind
groupings, that can be instantiated together, while deferring the
implementation and activation of such groups.
Generally speaking, the big idea is to provide several well known
group 'aliases', for example, bind.Global, bind.User or bind.Lsp,
and let users override key binds in these groups, while the actual
functionality is provider (Bind.action) is opaque to them.
This is a much prettier frontend for the vim.notify API, which is used
by a lot of plugins to communicate information and/or errors.
Try it out yourself:
:lua vim.notify('Hello, world!', 'info', { title = 'Testing Notify'})
- Enable toggleterm support (it now recognizes TT windows)
- Use gitsigns for branch detection (faster than running external
git commands)
- Remove 'italic' from branch section highlights
This change moves the original module loading utilities to
util/mload.lua, while providing a shim object that lazily attempts to
locate a function that matches the name of the indexed object.
This changes allows me to better organize utility functions
So story time, I discovered :checkhealth in Neovim, and it gave a fairly
decent explanation of how to fix terminal truecolor support.
Namely, use `tmux-256color` (or `screen-256color`) for the
default-terminal, then force truecolor (Tc) in the terminal-overrides
It also mentioned that `focus-events` needs to be enabled for n/vim to
detect changes to its buffers. Notably, this allows vim to rerender
changed content when switching into a tmux pane containing a vim
session.
Unfortunately pear-tree seems to conflict with coc in utilizing <CR>
(enter). Also the previous function assigned to <C-Space> wasn't very
useful (triggering autocompletion menu) as <TAB> already handles that.
The help (K) keymap was referencing a helper object that was spuriously
left in during the development of e5909ca. This fixes that mistake, and
should remove the 'global object coc is undefined' errors that occurred
in pressing the keybind.
This commit also fixes a 1 character mistake in the pum selection logic
for confirming selection. It should now just autocomplete every item as
they are <TAB>'d through.
coc.nvim introduced a metric ton of backwards incompatible changes to
various APIs they expose in Vim.
This commit updates the bits we use to use the new way of doing things.
It also adds a :Format command that can be used to format the current
buffer.
You'll need to do a :PlugUpdate if your psoxizsh has an old coc locally,
you can check your version with :CocInfo, if the `version` is <= v0.0.79
It appears that during rearranging yonks ago we accidentally sourced
oh-my-zsh before we set this setting, leading to the ssh-agent _always_
creating a new agent, even when SSH_AUTH_SOCK had already been set.
This a fairly minor problem, but it does leave to session lingering, and
breaks programs that manage ssh-agent identities, like gnome-keyring, or
systemd user session ssh-agent services.
this allows users to add a custom 'highlights' object to the top level
object passed to bufferline's setup/1 method, rather than only allowing
them to override the 'options' sub-object. See h: bufferline-highlights
for more on how to configure this.
Basically, a whole bunch of crap was changed in 0.80, and this fixes our
config to use the new way of doing things.
*important* to retain the old way of <TAB> _not auto selecting the first
element_ in a completion window you must set '"suggest.noselect": true'
in your CocConfig! This was previously true by default, but now is false
by default.
Paul Stemmet
psox