Because of DPMS, I would still get a screen-lock after a 10-minute
timeout.
I think the `xset s {on,off}` part is not _strictly_ necessary, but a
little bit of cargo-culting never hurt anybody.
According to the `xss-lock` man page `xset s on` use hard-coded values,
not my preferred timeouts. Given that I rely on `xautolock` anyway, I
don't care about the timeouts and set them to `0`.
Only for the configuration, not `LESS`, as settings it through the
configuration file does not result in the behaviour I want in Git (and
probably other programs).
Home-Manager now warns (loudly) about relying on legacy defaults on
older state versions.
I'd rather update to the newer state version than explicitly silence
those warnings by setting options I do not care for. The new defaults
are better anyway.
The upstream commit [1] said it was a non-breaking change, but didn't
actually setup the symlinks for this package...
[1]: 10f01ded353d5a76c6acbecaa0ac5e5063f60c13
It's gated behind `completionSync.enable`, as it does make
entering/leaving direnv-enabled projects slower (due to the calls to
`compinit`).
This might need a bit more work to avoid multiple `compinit`s at shell
startup, will refine in the future if necessary.
Despite what I just said in the previous commit, I decided to remove the
`is_executable` checks and always enable all servers.
I figured out that NeoVim actually handles `PATH` modifications pretty
well in this scenario: making a previously unavailable server executable
will automatically enable it.
The `nvim-lspconfig` "framework" is being deprecated to use the native
`vim.lsp.config` and `vim.lsp.enable` functionality.
I _could_ remove the `is_executable` checks, as native LSP handling does
_not_ loudly error out when enabling a server which isn't executable.
However I think `:LspInfo` is more readable if I don't.
Ideally, I'd like for `delta` to just read a configuration file at
`$XDG_CONFIG_HOME/delta/config` by default, but upstream seems somewhat
reticent to the idea :-/.
So instead, let's keep relying on `git` being enabled, but rather than
inlining the configuration, let's store it where I think it should
belong and include it into `gitconfig`.
