Commit graph

118 commits

Author SHA1 Message Date
Bruno BELANYI 95df872916 home: vim: add 'gitsigns-nvim' 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 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
Bruno BELANYI d7a9783ceb home: vim: keep space after shell redirections 2022-03-02 12:30:53 +01:00
Bruno BELANYI f54fbcf793 home: vim: show error codes from 'shellcheck' 2022-03-02 12:30:53 +01:00
Bruno BELANYI 4b92a3fda9 home: vim: configure 'null-ls' for 'python' 2022-03-02 12:30:53 +01:00
Bruno BELANYI 5947ec4217 home: vim: configure 'null-ls' for 'cpp' 2022-03-02 12:30:53 +01:00
Bruno BELANYI bb512cf838 home: vim: configure 'null-ls' for 'c' 2022-03-02 12:30:53 +01:00
Bruno BELANYI 3aa859861e home: vim: add formatting on save with 'null-ls' 2022-03-02 12:30:53 +01:00
Bruno BELANYI 60b87c90fc home: vim: configure 'null-ls' for 'haskell' 2022-03-02 12:30:53 +01:00
Bruno BELANYI 5f06b43ad4 home: vim: configure 'null-ls' for 'zsh' 2022-03-02 12:30:53 +01:00
Bruno BELANYI 58470804d6 home: vim: configure 'null-ls' for 'sh' 2022-03-02 12:30:53 +01:00
Bruno BELANYI 58bf5b6b1c home: vim: configure 'null-ls' for 'bash' 2022-03-02 12:30:53 +01:00
Bruno BELANYI 367dc1e5a5 home: vim: add 'null-ls' 2022-03-02 12:30:53 +01:00
Bruno BELANYI d9a2c12d3f home: vim: configure 'lightline-lsp'
This pretty much replace 'lightline-ale' for me now.

At least it will, once I have configured some LSP clients.
2022-03-02 12:30:53 +01:00
Bruno BELANYI f73f59b06c home: vim: add 'lightline-lsp' 2022-03-02 12:30:53 +01:00
Bruno BELANYI cb389b71b1 home: vim: remove 'quickfixed' functionality
I never use it anymore...
2022-03-02 12:13:13 +01:00
Bruno BELANYI 4382904060 home: vim: remove 'ALE' configuration
First step to modernising my configuration to use the native LSP client
instead.
2022-03-02 12:13:13 +01:00
Bruno BELANYI d2e410de56 home: vim: fix icon for read-only files 2022-02-23 21:06:12 +01:00
Bruno BELANYI 876dacab85 home: vim: cut back on fzf mappings
I only ever use the buffer and files regularly.
2021-12-22 23:34:46 +01:00
Bruno BELANYI 4055ef17f0 home: vim: switch back to gruvbox theme
All checks were successful
continuous-integration/drone/push Build is passing
Onedark is too annoying to deal with, and I still like gruvbox's colors
best.
2021-09-29 18:50:33 +02:00
Bruno BELANYI 859135880e home: vim: remove BetterWhitespace commands 2021-03-31 17:56:36 +00:00
Bruno BELANYI e92c46fc6d home: vim: make it enable-able 2021-03-14 12:18:09 +00:00
Bruno BELANYI 131ee2ceeb home: vim: add some wrapper plugins 2021-03-03 17:02:49 +00:00
Bruno BELANYI fdc150bea2 home: vim: refactor linked directories
This is more DRY.
2021-03-03 17:02:49 +00:00
Bruno BELANYI f1e4a4d914 home: vim: add 'after' 2021-03-03 17:02:49 +00:00
Bruno BELANYI d74aead9ae home: vim: add 'autoload' 2021-03-03 17:02:49 +00:00
Bruno BELANYI 300e16dace home: vim: add 'ftdetect' 2021-03-03 17:02:49 +00:00
Bruno BELANYI 6ea69fae87 home: vim: add 'plugin' directory 2021-03-03 17:02:49 +00:00
Bruno BELANYI 1e6a5401ec home: vim: disable 'termguicolors'
I forgot that I actually prefer the look without it.
2021-03-03 17:02:49 +00:00
Bruno BELANYI 513c1555f1 home: vim: load 'onedark-vim' manually 2021-03-03 17:02:49 +00:00
Bruno BELANYI e5f4416a85 home: vim: add 'init.vim' 2021-03-03 17:02:49 +00:00
Bruno BELANYI 828c1663da home: vim: add plugins
Pretty much every one that was in my dotfiles
2021-03-03 17:02:49 +00:00
Bruno BELANYI 5d508771ce home: add vim
This actually uses neovim... I'm done with trying to be compatible with
both I haven't actually migrated my configuration to it yet, this is not
even the bare minimum.

We'll get there :-)
2021-03-03 17:02:49 +00:00