21a5705631
home: jj: use verbose draft commit messages
2025-12-01 12:25:10 +00:00
0ba3d37813
home: delta: add 'jujutsu.enable'
2025-12-01 12:25:10 +00:00
5d511a029c
home: add jujutsu
...
This is a very basic configuration, still missing most bells and
whistles.
2025-12-01 12:25:09 +00:00
29fb7c5066
home: discord: use upstream module
ci/woodpecker/push/check Pipeline was successful
2025-11-17 13:58:13 +00:00
6e73c936b0
home: zsh: fix plug-in path
...
ci/woodpecker/push/check Pipeline failed
The upstream commit [1] said it was a non-breaking change, but didn't
actually setup the symlinks for this package...
[1]: 10f01ded353d5a76c6acbecaa0ac5e5063f60c13
2025-11-08 11:57:45 +00:00
bbdbc1e55c
home: vim: ftdetect: remove glsl
...
GLSL is now correctly detected starting with v0.11.
This reverts commit b8b64bed8e
2025-11-08 11:57:45 +00:00
0ac983a71f
home: vim: do not set 'background' explicitly
...
Rely on the new behaviour from v0.10 which detects it more
intelligently.
2025-11-08 11:57:45 +00:00
c536ee0136
home: zsh: add 'zsh-completion-sync'
...
ci/woodpecker/push/check Pipeline was successful
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.
2025-11-03 17:20:03 +01:00
4000a848ef
home: delta: use upstream module
2025-11-03 17:20:02 +01:00
9ddc77958a
home: git: fix deprecated config
2025-11-03 17:20:02 +01:00
6b1b5300cd
home: vim: lspconfig: simplify LSP config
...
ci/woodpecker/push/check Pipeline was successful
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.
2025-10-03 12:39:18 +00:00
62533d435b
home: vim: lspconfig: use native configuration
...
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.
2025-10-03 12:18:42 +00:00
9f9c1e571b
home: zsh: do not notify on 'home-manager news'
ci/woodpecker/push/check Pipeline was successful
2025-09-18 10:03:12 +00:00
e6c95245b2
home: ssh: disable default config
...
ci/woodpecker/push/check Pipeline was successful
It's been deprecated.
This also makes my `addKeysToAgent` configuration more explicit.
2025-09-04 11:37:17 +00:00
3fa1664b5c
home: delta: use stand-alone configuration file
...
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`.
2025-09-04 11:20:57 +00:00
31147abd91
home: add trgui
2025-09-04 11:20:57 +00:00
a889dfbb1a
home: nix: fix renamed option
2025-09-04 11:20:57 +00:00
f3af8f9ba8
home: atuin: remove bad comment
...
Most likely a copy-paste error.
2025-08-21 12:07:10 +00:00
5f073875e6
home: tmux: use consistent commenting style
ci/woodpecker/push/check Pipeline was successful
2025-08-11 10:18:35 +00:00
8c506ea03c
home: xdg: enable 'preferXdgDirectories'
...
At the moment this only makes a difference for `dircolors`.
2025-08-11 10:05:19 +00:00
f94fc468aa
home: zsh: ignore more commands for notification
ci/woodpecker/push/check Pipeline was successful
2025-08-04 14:28:34 +00:00
2a515754a2
home: zsh: use absolute path to 'XDG_CONFIG_HOME'
...
ci/woodpecker/push/check Pipeline was successful
The path handling has been fixed upstream, which makes this module more
readable.
2025-07-27 20:49:36 +01:00
13b61346f5
home: tmux: increase history scrollback
...
ci/woodpecker/push/check Pipeline was successful
Even *longer*.
2025-07-16 14:50:16 +00:00
2473bca167
home: vim: telescope: remove LSP handlers
...
ci/woodpecker/push/check Pipeline was successful
The plug-in was broken with the update to 0.11, and I would like to try
using the built-in quickfixlist-based handlers for a while.
This reverts commit 8d4a1e61b4
2025-07-11 14:27:51 +00:00
112e340361
home: do not hard-code username
...
ci/woodpecker/push/check Pipeline was successful
The flake module already sets it with `mkDefault`, making it easier to
override it for a specific host.
2025-06-17 09:29:30 +00:00
98d39717e2
home: direnv: lib: don't erase pre-existing venv
...
ci/woodpecker/push/check Pipeline was successful
Turns out `uv venv` isn't idempotent, it removes the existing virtual
environment by default.
Thankfully, there's a flag to fix it.
2025-05-31 22:39:25 +01:00
a9ba93f834
home: delta: assert git is enabled
ci/woodpecker/push/check Pipeline failed
2025-05-07 11:27:12 +00:00
d2a8894eb2
home: wm: i3: make 'firefox' history float
ci/woodpecker/manual/check Pipeline failed
2025-05-05 18:06:46 +01:00
22f97b4ac7
home: vim: lua: lsp: configure inlay hints
2025-05-03 13:56:12 +01:00
4b6f62b25a
home: gpg: fix deprecated config
ci/woodpecker/push/check Pipeline failed
2025-04-30 21:39:39 +01:00
89bc60609f
home: firefox: tridactyl: use 'replaceVars'
ci/woodpecker/push/check Pipeline failed
2025-04-24 12:46:24 +02:00
946eab9ec0
home: git: extract 'delta' configuration
...
ci/woodpecker/push/check Pipeline was successful
I want to be able to re-use it between different source control systems
(e.g: `jj`).
As a first step, extract it to a proper module so that I can have it
live in a single space.
2025-04-22 13:53:35 +00:00
ec1c94676a
home: vim: highlight over-extended commit subjects
ci/woodpecker/push/check Pipeline was successful
2025-04-22 13:15:04 +00:00
29b47d7f84
home: tmux: rename 'mkTerminalFeature'
...
This is a more accurate name to describe what the function is doing.
2025-04-22 13:04:36 +00:00
135cef2536
home: atuin: add daemon
...
ci/woodpecker/push/check Pipeline was successful
Enabled by default, I probably won't have a reason *not* to use it.
2025-04-16 16:05:14 +00:00
26ee59ef6e
home: atuin: use 'uk' dialect for dates
...
ci/woodpecker/push/check Pipeline was successful
This should be for date *parsing*, from my looking at the code.
Unlikely to be relevant, but might as well set it to the saner of the
two options.
2025-04-14 13:54:57 +00:00
6f5ac4e55f
home: vim: signtoggle: only show signs if 'number'
...
ci/woodpecker/push/check Pipeline was successful
If a buffer doesn't show a number column, I probably also don't want a
sign column to be toggled on/off in there.
2025-04-14 10:24:33 +00:00
67936af4c7
home: vim: signtoggle: remove 'TermOpen' event
...
It's now part of upstream's default setup.
2025-04-14 10:20:02 +00:00
e82ae4a219
home: vim: numbertoggle: remove 'TermOpen' event
...
It's now part of upstream's default setup.
2025-04-14 10:20:02 +00:00
d48d5c45e0
home: vim: remove 'friendly-snippets'
...
I never use them...
2025-04-04 19:06:19 +01:00
36aa641ec0
home: vim: rely on built-in diagnostic jump config
...
This reduces the surface area of my configuration.
2025-04-03 22:04:44 +01:00
2583cc6c12
home: vim: lua: lsp: add count to diagnostic maps
2025-04-03 22:04:44 +01:00
262dc48425
home: vim: use default 'diffopt:linematch'
...
It's now been defaulted to `linematch:40` on v0.11.
2025-04-03 22:04:44 +01:00
c1efc4316d
home: vim: lualine: add custom 'oil' extension
...
I don't like the built-in one.
2025-04-03 22:04:44 +01:00
4ef1b08f4e
home: vim: lualine: use built-in 'branch'
...
It now supports worktrees correctly (or at least I can't figure out
which issue I used to have with it...).
As a bonus, it also supports showing the correct branch for an `oil`
buffer.
This reverts commit 481d5f6f53
2025-04-03 22:04:44 +01:00
274d143031
home: vim: fix deprecated calls
2025-04-03 22:04:44 +01:00
dfb3c353ec
home: vim: remove 'lsp_lines'
...
It's been upstreamed!
2025-04-03 22:04:44 +01:00
37e88c2707
flake: bump inputs
...
And fix the small `jq` breakage.
2025-04-03 22:04:44 +01:00
458ea144c4
home: vim: remove 'fastfold' configuration
...
I missed it in the original commit that removed the plug-in from my
configuration...
2025-04-02 20:42:40 +01:00
abec0dd226
home: git: remove 'ignoreRevsFile'
...
I remember why I didn't set it globally now, it's because `git blame`
complains and errors out, rather than silently ignoring the setting,
when the file doesn't exist in a repo...
This reverts commit 5ae2eacd49
2025-04-02 20:42:40 +01:00
