337d7309c6
home: git: use 'mkAfter' for config includes
...
ci/woodpecker/push/check Pipeline was successful
This should ensure that they will be included at the very end of the
configuration, even if other modules add more includes.
Notably, this ensures that the local configuration can override any
other setting.
2025-02-24 14:02:06 +00:00
1237ef4174
home: git: include local configuration properly
...
ci/woodpecker/push/check Pipeline was successful
Using `includes` ensures that the local configuration is included at the
end of the configuration file.
2025-02-21 16:22:44 +00:00
80b4c9ffcd
home: mail: accounts: use 'migadu' flavor
2025-02-13 22:55:25 +01:00
9c4d853037
home: secrets: github: update token
2025-02-13 22:55:25 +01:00
2cbcbb7b3a
home: secrets: fix path to 'keys'
2025-02-13 22:55:25 +01:00
e65b3ed1fc
home: vim: ftplugin: add query
ci/woodpecker/push/check Pipeline was successful
2024-12-23 22:42:42 -05:00
b7b6705391
home: wm: i3: make 'arandr' float
...
ci/woodpecker/push/check Pipeline was successful
Another work-around due to a wrapper in nixpkgs.
2024-12-18 20:48:09 -05:00
ead8101b8d
home: wm: i3: match 'blueman' float explicitly
...
This is more of a work-around due to the wrapper in nixpkgs' packaging
of that application, so might as well make that explicit and narrow.
2024-12-18 20:48:09 -05:00
c75a307c58
home: wm: i3: fix 'pavucontrol' float
ci/woodpecker/push/check Pipeline was successful
2024-12-18 20:39:15 -05:00
322fbc970b
home: vim: lsp: rely on 'bashls' formatting
...
ci/woodpecker/push/check Pipeline was successful
I finally figured out why I was getting the wrong indentation, turns out
it was an issue in `lsp-format.nvim`. With that fixed/worked around, I
can now rely completely on `bash-language-server` for formatting.
I'll also rely on `shfmt` automatically detecting the type of file, as
(Neo)Vim cannot be made to reliably set `ft=bash` for Bash scripts and
`ft=sh` for POSIX shell.
Finally, I removed spaces after redirections, I've now come around to
liking the default (no spaces) better.
2024-12-18 20:20:28 -05:00
35c547a090
home: tmux: enable focus events
...
ci/woodpecker/push/check Pipeline was successful
Since `tmux-sensible` was disabled by default, we should enable this
explicitly now.
2024-12-08 10:44:26 -05:00
3ac85b8762
home: packages: add 'tree'
2024-12-08 10:44:26 -05:00
98c90d77c5
home: tmux: add sloppy window switching bindings
...
Another set of bindings which were setup by `tmux-sensible`, that I want
to enable explicitly to avoid issues when it is disabled by default.
2024-12-08 10:44:26 -05:00
b38658405a
home: tmux: add binding to refresh configuration
...
Don't rely on `tmux-sensible` to set it up.
2024-11-28 18:39:09 +00:00
da3c29bbaf
home: xdg: add comment about 'tig'
...
To explain why I didn't modify it as part of my `$XDG_STATE_HOME`
migration in fbd3b70d61 .
2024-11-28 12:07:52 +00:00
8b61af1ac3
home: xdg: remove 'gdb' directory
...
I have an actual module to configure `gdb`, and it uses
`$XDG_STATE_HOME` anyway...
2024-11-28 12:07:12 +00:00
e8a41187e7
home: xdg: create 'HISTFILE' parent directory
...
In fbd3b70d61 , I forgot to modify the
`.keep` file to be created in `$XDG_STATE_HOME/bash/`.
2024-11-28 12:06:03 +00:00
83da7ba9c8
home: tmux: explicitly disable mouse support
...
ci/woodpecker/push/check Pipeline was successful
It's disabled by default, but make it explicit :-).
2024-11-28 11:24:34 +00:00
f2168378fc
home: direnv: lib: also watch '.python-version'
...
ci/woodpecker/push/check Pipeline was successful
It's used by `uv` as a kind of configuration file, so watch it as well.
2024-11-27 15:12:10 +00:00
62de2772a4
home: vim: do not italicize comments
ci/woodpecker/push/check Pipeline was successful
2024-11-05 15:54:18 +00:00
8475d92314
home: nix: configure GC
ci/woodpecker/push/check Pipeline was successful
2024-10-30 10:33:50 +00:00
46df8b5b5b
home: direnv: lib: fix shellcheck directive
...
ci/woodpecker/push/check Pipeline was successful
I like it better with a space in it.
2024-10-23 13:49:28 +00:00
0547ebc33c
home: wm: i3: remove 'FIXME'
...
ci/woodpecker/push/check Pipeline was successful
Add a clearer message about why I don't use the `startup` section.
2024-10-16 10:43:52 +00:00
8e81d148bd
home: direnv: warn on non-existent version
ci/woodpecker/push/check Pipeline was successful
2024-10-10 13:56:27 +00:00
38f3ac0ce5
home: vim: lspconfig: add 'typos-lsp'
ci/woodpecker/push/check Pipeline was successful
2024-09-27 14:11:03 +00:00
898523d079
treewide: fix typos
2024-09-27 13:49:29 +00:00
8d344b5d51
home: direnv: add 'layout_uv'
...
ci/woodpecker/push/check Pipeline was successful
I haven't really played with it yet, but from my small experiments this
should be good enough for my (future) purposes.
2024-09-12 13:23:19 +00:00
8a6af0e5b7
home: direnv: only mention 'poetry init'
...
ci/woodpecker/push/check Pipeline was successful
`poetry new` creates a new directory, which isn't really what we're
interested in here.
2024-09-12 12:08:50 +00:00
4f73945e28
home: direnv: silence 'layout_poetry'
2024-09-12 12:07:22 +00:00
6529bea6bb
home: nixpkgs: don't use 'escapeShellArg'
...
ci/woodpecker/push/check Pipeline was successful
I don't know what I was thinking exactly when I wrote this, but I
clearly hadn't tested it. We can't use `escapeShellArg` as we need to
expand the `$XDG_RUNTIME_DIR` variable used in those paths...
This reverts commit 468eaa9ed4 .
2024-09-11 10:28:32 +00:00
e67b055a7b
home: vim: fix unimpaired mapping groups
ci/woodpecker/push/check Pipeline was successful
2024-09-09 21:40:54 +01:00
fbd3b70d61
home: use 'XDG_STATE_HOME' for history files
...
ci/woodpecker/push/check Pipeline was successful
It's specified as the place to put them, so let's make use of it I
guess.
2024-09-06 20:52:30 +01:00
1e2872c5c7
home: vim: fix '+'/'-' highlighting in diffs
...
ci/woodpecker/push/check Pipeline failed
I'm not a big fan of the new highlighting [1].
[1]: https://github.com/nvim-treesitter/nvim-treesitter/pull/6619
2024-07-27 15:09:52 +01:00
9ed2dcefde
home: vim: which-key: use lua callbacks
ci/woodpecker/push/check Pipeline failed
2024-07-26 11:54:11 +00:00
0d820cc2f4
home: vim: move 'nohls' to 'which-key'
2024-07-26 11:52:17 +00:00
6b7510cfd9
home: vim: show directories in blue
...
ci/woodpecker/push/check Pipeline failed
Blue is much more readable when the night filter kicks in.
2024-07-25 20:32:15 +01:00
58760280be
home: vim: update for 'which-key' v3
...
It complains quite loudly about the legacy mapping syntax.
2024-07-25 20:32:15 +01:00
d04de7d213
flake: bump inputs
...
And fix renamed packages.
2024-07-25 20:32:15 +01:00
442eef0482
home: vim: git: fix deprecated functions
ci/woodpecker/push/check Pipeline was successful
2024-07-25 09:39:38 +00:00
997f208d30
home: vim: remove irrelevant filetype plugins
...
I don't make use of their non-upstreamed functionality.
2024-07-24 16:33:09 +00:00
326f9d039a
home: vim: disable 'swapfile'
...
ci/woodpecker/push/check Pipeline was successful
As before, I still dislike this option and find its downsides worse than
its upsides.
2024-07-22 16:05:54 +00:00
abaa7119e7
home: vim: consistent 'unimpaired' mapping names
ci/woodpecker/push/check Pipeline was successful
2024-07-20 11:34:42 +01:00
c6735f3912
home: vime: tree-sitter: remove 'which-key'
...
ci/woodpecker/push/check Pipeline was successful
The plug-in now has support for setting mapping descriptions by itself.
2024-07-19 11:38:55 +00:00
3438290e32
home: vim: tree-sitter: move mappings from 'after'
2024-07-19 11:38:55 +00:00
82f49f1389
home: vim: telescope: move mappings from 'after'
2024-07-19 11:38:55 +00:00
5918a0b9e6
home: vim: signtoggle: use lua callbacks
...
Use `vim.opt` because this is a local option (i.e: similar to `set` it
defaults to setting it locally, `vim.opt_local` is not necessary).
2024-07-19 11:38:55 +00:00
a7c542784c
home: vim: numbertoggle: use lua callbacks
...
Use `vim.opt` because those are local options (i.e: similar to `set` it
defaults to setting it locally, `vim.opt_local` is not necessary).
2024-07-19 11:38:55 +00:00
280829b54f
home: vim: signtoggle: fix toggling
...
Don't know how I missed this for so long...
2024-07-19 11:38:55 +00:00
5ffe2653c0
home: vim: git: work around partial staging issue
...
See [1].
[1]: https://github.com/lewis6991/gitsigns.nvim/issues/929
2024-07-19 11:38:54 +00:00
5592a120a4
home: vim: git: use 'partial'
2024-07-19 11:38:54 +00:00