Commit graph

44 commits

Author SHA1 Message Date
Bruno BELANYI bcbc9af372 home: vim: telescope: set-up 'fzf' matching 2022-03-08 10:41:35 +01:00
Bruno BELANYI 16fc677509 home: vim: replace 'fzf' with 'telescope'
I like the fact that it uses built-in buffers to preview files.

It also has more inertia behind it, tighter integrations in the
ecosystem.
2022-03-08 10:41:35 +01:00
Bruno BELANYI 9ef35f06df home: vim: completion: limit 'buffer' suggestions
Otherwise it gets overwhelming, and most are useless.
2022-03-08 10:41:35 +01:00
Bruno BELANYI 5b7fa7c09a home: vim: completion: use better order 2022-03-08 10:41:35 +01:00
Bruno BELANYI a49e66da80 home: vim: completion: use native menu 2022-03-08 10:41:35 +01:00
Bruno BELANYI 35d96e1e69 home: vim: configure 'nvim-cmp' for LSP 2022-03-08 10:41:35 +01:00
Bruno BELANYI 273618ff94 home: vim: configure 'nvim-cmp' 2022-03-08 10:41:35 +01:00
Bruno BELANYI 3df2ad0f1f home: vim: git: more visual mappings
I cannot use the functions directly, as I would need to calculate the
current selections begin and end points and use them as arguments.

To be investigated.
2022-03-04 17:40:30 +01:00
Bruno BELANYI 57e5def998 home: vim: git: 'gitsigns' mappings are per buffer 2022-03-04 17:40:30 +01:00
Bruno BELANYI c5d9396a7d home: vim: git: use more appropriate mapping names 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 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 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 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 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 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 ae7c2d921b home: vim: add statement objects/moves
And document it.
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 b7b3387df7 home: vim: add 'treesitter-textobjects' 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 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 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 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 3aa859861e home: vim: add formatting on save with 'null-ls' 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 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 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 fdc150bea2 home: vim: refactor linked directories
This is more DRY.
2021-03-03 17:02:49 +00:00
Bruno BELANYI 6ea69fae87 home: vim: add 'plugin' directory 2021-03-03 17:02:49 +00:00