Commit graph

168 commits

Author SHA1 Message Date
cecb7d9bb4 home: vim: lspconfig: configure diagnostics once
All checks were successful
ci/woodpecker/push/check Pipeline was successful
There's no need to configure it on each LSP attach, this is wasted work
and could change options that have since been changed.
2023-06-22 15:35:32 +00:00
39a512bc0a home: vim: unset 'splitkeep'
All checks were successful
ci/woodpecker/push/check Pipeline was successful
Turns out I do _not_ like this behaviour when it messes with the cursor
position.

If they had an option that kept my cursor correctly positioned, and only
then tried to move the buffer to keep it steady, I'd try it.

This reverts commit 4feee73b8e.
2023-06-01 11:34:09 +00:00
5de4ee93d5 home: vim: use smarter diagnostics float display
All checks were successful
ci/woodpecker/push/check Pipeline was successful
2023-05-31 14:00:32 +00:00
41df5c01ad home: vim: ftdetect: add kconfig
All checks were successful
ci/woodpecker/push/check Pipeline was successful
2023-05-12 12:31:07 +00:00
153b6a43cc home: vim: ftdetect: add kbuild 2023-05-12 12:28:06 +00:00
527a85bf11 home: vim: ftdetect: switch to lua
It looks like `vim.filetype.add` is smarter about "local.am".

For some reason opening an *empty* Tiger file results in a backtrace...
2023-05-12 12:26:56 +00:00
01059616bf home: vim: don't use 'nixpkgs-fmt' with 'nil'
All checks were successful
ci/woodpecker/push/check Pipeline was successful
2023-05-09 20:25:15 +01:00
8a78ce8520 home: vim: null-ls: add 'buildifier' configuration 2023-05-09 20:23:07 +01:00
102dc4cc76 home: vim: null-ls: restrict POSIX to bare 'sh' 2023-05-09 20:22:12 +01:00
1e9f6fe957 home: vim: fix lua formatting 2023-05-07 13:36:10 +01:00
c2d231d3f1 home: vim: use actual lua files
Since most of the settings are actually just lua in a VimL file.
2023-05-07 13:36:10 +01:00
9530864b10 home: vim: fastfold: use lua configuration 2023-05-07 13:36:10 +01:00
e599a97e45 home: vim: abbreviations: use lua
This makes it less repetitive.
2023-05-07 13:36:10 +01:00
39c2e5db8c home: vim: signtoggle: use lua autocommands
A nice next step would be to use actual lua callbacks instead of the
VimL command.
2023-05-07 13:36:10 +01:00
dba8836381 home: vim: numbertoggle: use lua autocommands
A nice next step would be to use actual lua callbacks instead of the
VimL command.
2023-05-07 13:36:10 +01:00
36b0c67832 home: vim: completion: use lua settings 2023-05-07 13:33:02 +01:00
68b9c3b9b1 home: vim: remove 'vim-pandoc'
The tree-sitter code-block high-lighting is built-in and works better,
and I don't use any of the other features.
2023-05-07 13:04:37 +01:00
46d9e5c829 home: vim: lspconfig: add 'nil'
All checks were successful
ci/woodpecker/push/check Pipeline was successful
2023-05-04 09:27:19 +00:00
4feee73b8e home: vim: set 'splitkeep' 2023-05-03 20:02:34 +01:00
7bd2e1504d home: vim: lua: lsp: customize diagnostics display 2023-05-03 15:02:44 +00:00
b0f054b1e6 home: vim: configure 'lsp_lines' 2023-05-03 15:02:44 +00:00
6cdbd6bb29 home: vim: lua: lsp: remove diagnostic on hover 2023-05-03 15:02:44 +00:00
5c372cfa95 home: vim: use 'exrc'
Remove the home-grown "solution" that I had stolen from school (and
never used...) for project-local configuration.

Since [1], it is okay to use the built-in vim option for this, since it
only asks for user-input before trusting a file.

Since [2] they even support lua files!

[1]: https://github.com/neovim/neovim/pull/20956
[2]: https://github.com/neovim/neovim/pull/21436
2023-05-03 15:02:44 +00:00
e9f07e67dc home: vim: add diff line matching
All checks were successful
ci/woodpecker/push/check Pipeline was successful
This should bring more readable diffs. See [1].

[1]: https://github.com/neovim/neovim/pull/14537
2023-04-19 08:36:40 +00:00
2375f88e56 home: vim: use patience diff
This brings it in line with my `git` configuration.
2023-04-19 08:34:39 +00:00
84fc1601c5 home: vim: 'unimpaired' mappings for formatting
All checks were successful
continuous-integration/drone/push Build is passing
I'll migrate to calling the lua API directly if they stop expecting a
non-nil argument.
2023-03-20 09:52:05 +00:00
0241bfc781 home: vim: modify 'unimpaired' quickfix mappings 2023-03-20 09:52:05 +00:00
20341a3129 refactor: 'with lib.my' -> 'with lib' 2023-03-16 16:42:55 +00:00
623bb6c893 home: vim: git: attach to untracked buffers
All checks were successful
continuous-integration/drone/push Build is passing
Turns outs it looks way more discreet now. Whether that's due to an
update to the plug-in or my changing colorscheme, I don't know.
2023-03-13 15:49:07 +00:00
41bd17e3ca home: vim: migrate to 'gruvbox-nvim'
I think this one will be more up-to-date with NeoVim evolutions, like
LSP semantic tokens.
2023-03-07 11:05:07 +00:00
a29deaa9bc home: vim: use 'lsp-formatting.nvim'
A few things that are different:
* Async by default.
* Takes care of the order of formatters, if I ever need to do that.
* Allows for easily disabling formatting (unfortunately this is global
  state, not buffer-local).
* Gets rid of the formatting pause when doing `:wq`.
2023-03-07 11:05:07 +00:00
3122db6536 home: vim: disable mouse integration 2023-03-07 11:05:07 +00:00
225e8f236e home: vim: ftdetect: add direnv
All checks were successful
continuous-integration/drone/push Build is passing
2023-02-17 15:53:55 +00:00
2ffb8e6ee6 home: vim: add 'nvim-osc52'
All checks were successful
continuous-integration/drone/push Build is passing
I do get the message when copying into the clipboard while ssh-ing.

But trying to paste from my system clipboard shows that it did *not* get
copied. This seems to only happen inside tmux.

However tmux itself *does* copy to the clipboard correctly through OSC52.
2023-02-12 11:55:58 +00:00
e04fa74412 home: vim: lua: utils: add 'is_ssh'
All checks were successful
continuous-integration/drone/push Build is passing
2023-02-11 22:17:22 +00:00
2b3fb4fa5a home: vim: use shorter tree-sitter alias 2023-02-08 14:03:23 +00:00
4971634115 home: vim: make it the default editor explicitly 2023-02-07 14:19:50 +00:00
b4d745c50e home: vim: add 'cmp_luasnip'
I had forgotten to add it even though I configured it as a source...
2023-01-20 19:16:20 +00:00
19e42cdc26 home: vim: reorder snippet plugins 2023-01-20 19:15:31 +00:00
5f3299e383 home: vim: luasnip: use lazy-loading 2023-01-20 19:10:14 +00:00
16d4147321 home: vim: lspconfig: update deprecated call 2022-11-03 18:07:00 +01:00
236d48befb home: vim: lua: lsp: update for nvim 0.8
Two big changes:

* Making use of the lua API for creating autocmds.
* Using `client.supports_method`.
2022-11-03 18:07:00 +01:00
3c3e56002f home: vim: add 'nix' ftplugin 2022-10-26 14:14:01 +02:00
4216c654e7 home: vim: migrate to 'nvim-surround'
It's potentially more customizable, and integrates with tree-sitter. It
also allows for buffer/filetype specific pairs.
2022-09-02 09:56:20 +02:00
9f82981602 home: vim: add 'nvim-lspconfig'
For some reason I had not added it to my plug-in list, but it still
worked until I bumped my inputs.
2022-06-23 10:02:32 +02:00
7e4e41a07f home: vim: add 'tiger' file-type configuration 2022-06-20 14:33:44 +02:00
341450db5c home: vim: ftdetect: add tiger 2022-06-15 11:27:03 +02:00
489b79f078 home: vim: completion: activate 'ghost_text'
I'm still thinking whether I would want to use one of those signature
helper windows to go with this/replace this feature.

Could be especially useful in C++.
2022-05-19 14:53:09 +02:00
93e50508c9 home: vim: lua: lsp: add signature help mapping 2022-04-27 14:02:17 +02:00
e591344eb3 home: vim: git: map keys on start
Instead of mapping those keys when `gitsigns` attaches to a buffer...
2022-04-27 14:02:17 +02:00