457d4841ea
home: wm: i3: use grey background
...
Because I sometimes do get a glimpse of the background, and would rather
not have anything on it.
2026-04-04 23:05:58 +01:00
8e0ea3593c
home: firefox: tridactyl: refactor editor float
...
Ghostty *needs* a specific format for its `--class`, but not for its
`--title`.
2026-04-04 23:05:58 +01:00
70f651c5fa
home: firefox: tridactyl: refactor vim command
...
Thus far, I've only encountered `termite` having a broken implementation
of `--exec`...
2026-04-04 23:05:58 +01:00
6a7037f2a6
home: terminal: termite: add 'enable'
2026-04-04 23:05:58 +01:00
4d9bab8daf
home: terminal: alacritty: add 'enable'
2026-04-04 23:05:58 +01:00
ea818e8584
home: terminal: make 'default' extensible
2026-04-01 20:04:43 +01:00
14299fc6e8
home: terminal: rename 'default'
...
It doesn't make the *most* sense as an option name to use `program`.
2026-04-01 20:04:43 +01:00
b0fab6d576
home: terminal: use 'colors' directly
2026-04-01 20:04:43 +01:00
c7c593ff93
home: terminal: use 'colors' directly
2026-04-01 20:04:43 +01:00
8624f4c6ac
home: pager: use colored UI
2026-04-01 20:04:43 +01:00
3b7a119151
home: pager: add readline mappings
...
Found a nice tip to emulate deletion to start/end of line.
2026-04-01 20:04:43 +01:00
b1169858cd
home: pager: remove 'LESSHISTFILE'
...
It's now using an XDG-compliant value by default, I don't need to define
it myself.
2026-04-01 20:04:43 +01:00
fe7b0a57a8
home: pager: use long option names
...
Makes it more readable.
2026-04-01 20:04:43 +01:00
7a7da21a27
home: pager: use upstream module
...
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).
2026-04-01 20:04:43 +01:00
c3603a6191
home: pager: use explicit config section name
2026-04-01 20:04:43 +01:00
d111734802
home: firefox: disable AI features
...
As found on some HN thread, there may be more I have missed...
2026-04-01 20:04:43 +01:00
0f821729f1
home: set 'stateVersion' to '26.05'
...
ci/woodpecker/push/check Pipeline was successful
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.
2026-04-01 21:03:33 +02:00
d94f956434
flake: bump inputs
...
ci/woodpecker/push/check Pipeline was successful
And fix a package change.
2026-03-04 16:21:39 +00:00
b776c35692
treewide: remove redundant 'builtins'
...
I keep forgetting `map` and `removeAttrs` are included at the top-level
in the prelude.
2026-02-26 15:48:14 +00:00
354118ada1
treewide: remove unused 'with pkgs'
2026-02-26 15:48:14 +00:00
bfd058da36
home: vim: git: map hunk-navigation in more modes
ci/woodpecker/push/check Pipeline was successful
2026-02-04 20:40:33 +00:00
635fddc338
home: vim: migrate to new 'nvim-treesitter'
2026-02-04 20:40:33 +00:00
96a76f8c7f
home: vim: tree-sitter: migrate textobjects config
...
This uses the new configuration format. I might DRY it up at some point
in the future, though I probably won't.
2026-02-04 20:40:33 +00:00
28a36cfdaa
home: vim: use legacy 'nvim-treesitter' plug-ins
2026-01-26 16:59:58 +00:00
69b9480aa1
home: vim: git: use consistent textobject names
...
Specifically, use a lower-case name, to be consistent with all other
textobjects.
2026-01-26 16:59:58 +00:00
ab34234c83
home: vim: lua: remove 'is_executable_condition'
2026-01-26 16:59:58 +00:00
034a432c8e
home: vim: null-ls: use 'partial'
...
Just noticed that 'is_executable_condition' wasn't necessary now that I
have this more generic solution.
2026-01-26 16:59:58 +00:00
852ded641a
home: vim: lua: move 'list_clients' to lsp'
2026-01-26 16:54:00 +00:00
7202fa1911
home: firefox: do not trim URLs
ci/woodpecker/push/check Pipeline was successful
2025-12-20 14:56:43 +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
