Commit graph

838 commits

Author SHA1 Message Date
Bruno BELANYI adedb42a99 home: vim: add mappings for LSP functionality 2022-03-04 17:40:30 +01:00
Bruno BELANYI 38c140ee86 home: vim: don't use 'nixpkgs-fmt' with 'rnix' 2022-03-04 17:40:30 +01:00
Bruno BELANYI d36f01d937 home: vim: add 'rnix' LSP configuration 2022-03-04 17:40:30 +01:00
Bruno BELANYI 62f93a852a home: vim: add 'clang-tools' to vim package
It includes both `clangd` and `clang-format`, even though I'm mostly
looking for the later.
2022-03-04 17:40:30 +01:00
Bruno BELANYI 080d08bb13 home: vim: add linters & formatters to vim package
I use them so often, I basically always want them available.
2022-03-04 17:40:30 +01:00
Bruno BELANYI 6da1c47472 home: vim: add 'shellcheck' code actions 2022-03-04 17:40:30 +01:00
Bruno BELANYI 9c023b78a3 home: vim: rename 'git'-related settings file
Now that it contains more settings than just 'gitsigns'.
2022-03-04 17:40:30 +01:00
Bruno BELANYI 3d6580f52b home: vim: centralise 'git'-related mappings 2022-03-04 17:40:30 +01:00
Bruno BELANYI f34f2fc706 home: vim: configure 'gitsigns'
And remove some unused mappings, or adapt them to 'gitsigns'.
2022-03-04 17:40:30 +01:00
Bruno BELANYI 95df872916 home: vim: add 'gitsigns-nvim' 2022-03-04 17:40:30 +01:00
Bruno BELANYI 3e86aa5ef4 home: bat: use 'gruvbox-dark' theme
To match my `vim` configuration.
2022-03-04 17:40:30 +01:00
Bruno BELANYI f2f2b2a98a home: vim: prefer 'clangd' to 'clang-format'
Only use `clang-format` if `clangd` is not available, as its formatting
is otherwise built into the LSP server.
2022-03-04 17:40:30 +01:00
Bruno BELANYI 842489a986 home: vim: use 'unimpaired' mappings for quickfix 2022-03-04 17:40:30 +01:00
Bruno BELANYI 4cecb8b987 home: zsh: add 'zsh-completions' when enabled
Notably useful for `git-revise`.
2022-03-04 17:40:30 +01:00
Bruno BELANYI bc56292544 home: zsh: refactor 'mkIf' block 2022-03-04 17:40:30 +01:00
Bruno BELANYI c259fe87a0 home: zsh: use packaged 'fast-syntax-highlighting' 2022-03-04 17:40:30 +01:00
Bruno BELANYI 508b30eadd home: vim: show LSP progress in status line 2022-03-04 17:40:30 +01:00
Bruno BELANYI 605da54f24 home: vim: switch to 'lualine' 2022-03-04 17:40:30 +01:00
Bruno BELANYI 213d698d56 home: vim: add function to list LSP client names 2022-03-04 17:40:30 +01:00
Bruno BELANYI c5fff38942 home: vim: remove unused 'gruvbox' configuration 2022-03-04 17:40:30 +01:00
Bruno BELANYI e3b0f9d38f home: vim: move diagnostics config to 'on_attach' 2022-03-04 17:40:30 +01:00
Bruno BELANYI af56bc76cf home: vim: add 'clangd' LSP configuration 2022-03-04 17:40:30 +01:00
Bruno BELANYI 7a9760b0cd home: vim: add 'rust-analyzer' LSP configuration 2022-03-04 17:40:30 +01:00
Bruno BELANYI e8ffddedef home: vim: add basic LSP configuration
Trying it out with `pyright` for now.
2022-03-04 17:40:30 +01:00
Bruno BELANYI 44dae3a940 home: vim: move LSP-related 'on_attach' to 'utils'
As it will be shared between `null-ls` and `lspconfig`, it makes sense
to put it there.
2022-03-04 14:54:14 +01:00
Bruno BELANYI b79cee6eee home: vim: add diagnostic navigation mappings 2022-03-04 14:51:44 +01:00
Bruno BELANYI 56156e1fe4 home: vim: do not use 'ftplugin' for 'null-ls'
Unfortunately, this registers the sources many times...

I fear that I will have to settle for a centralised configuration for
LSP-related options.
2022-03-04 14:14:30 +01:00
Bruno BELANYI f551c4fc30 home: vim: only use 'null-ls' sources if available
This avoids the big red warning on each file that tries to use those
sources...
2022-03-03 18:15:28 +01:00
Bruno BELANYI f854c49c29 home: vim: add 'ambroisie.utils' lua module 2022-03-03 18:15:28 +01:00
Bruno BELANYI ae7c2d921b home: vim: add statement objects/moves
And document it.
2022-03-03 18:15:28 +01:00
Bruno BELANYI a96fb22d4d home: vim: document 'tree-sitter' moves 2022-03-03 18:15:28 +01:00
Bruno BELANYI bd5a15ebe7 home: vim: add 'tree-sitter' moves 2022-03-03 18:15:28 +01:00
Bruno BELANYI d26b9f2537 home: vim: document 'treesitter-textobjects' maps
By using 'which-key'.
2022-03-03 18:15:28 +01:00
Bruno BELANYI b7b3387df7 home: vim: add 'treesitter-textobjects' 2022-03-03 18:15:28 +01:00
Bruno BELANYI be84a4a6fa home: vim: remove mapping to run 'make' 2022-03-03 18:15:28 +01:00
Bruno BELANYI bbc47b6683 home: vim: document 'commentary' mappings
By using 'which-key'.
2022-03-03 18:15:28 +01:00
Bruno BELANYI 416a4ca0d6 home: vim: document 'unimpaired' mappings
By using 'which-key'.
2022-03-03 18:15:28 +01:00
Bruno BELANYI 19889f4cbf home: vim: use 'which-key' 2022-03-03 18:15:28 +01:00
Bruno BELANYI fa836d7df9 home: vim: add 'which-key-nvim' 2022-03-02 12:30:53 +01:00
Bruno BELANYI 8b985cda84 home: vim: move leader mappings to 'init.vim' 2022-03-02 12:30:53 +01:00
Bruno BELANYI 0478efa817 home: vim: remove unused mappings
The beancount mappings are absolutely unused.

The `Y` mapping is built in NeoVim nowadays.
2022-03-02 12:30:53 +01:00
Bruno BELANYI 87f255d265 home: vim: remove unimpaired mappings
I do not use `azerty` anymore, no need for those.
2022-03-02 12:30:53 +01:00
Bruno BELANYI b9e5273672 home: vim: remove 'lsp_lines'
I like the hovering behaviour better, it's less "in your face".

I might revisit the idea in the future, as a toggled mapping.
2022-03-02 12:30:53 +01:00
Bruno BELANYI dd3bfc74fa home: vim: show diagnostics on hover
Ideally, I want the following features:
* diagnostic icons in the sign column always,
* virtual text on the current line only
* switch to hover window and/or lsp_lines display through a mapping
2022-03-02 12:30:53 +01:00
Bruno BELANYI 5dd9d1c6d0 home: vim: configure short 'CursorHold' timeout 2022-03-02 12:30:53 +01:00
Bruno BELANYI d87fd7b9e1 home: vim: configure diagnostics further
This is not only 'lsp_lines' configuration anymore, but the whole
display of diagnostics.
2022-03-02 12:30:53 +01:00
Bruno BELANYI 01d7ead121 home: vim: add 'nvim-treesitter'
IMHO, this is *very* colorful, I might not end up using the highlighting
after all.

Let's see if I get used to it after a little while.
2022-03-02 12:30:53 +01:00
Bruno BELANYI e701dd06ea home: vim: make python formatting faster 2022-03-02 12:30:53 +01:00
Bruno BELANYI faa8ae6d1e home: vim: add 'lsp_lines'
I dislike the diagnostics *next* to affected lines.

This looks neater, though the best look would be a simple hover window
or status line message instead, like ALE used to do.

It might grow on me however.
2022-03-02 12:30:53 +01:00
Bruno BELANYI 729f60c471 home: vim: configure 'null-ls' for 'nix' 2022-03-02 12:30:53 +01:00