Restrict the default search to commits _starting_ with 'WIP:',
to avoid accidentally selecting commits which just contain the word
'WIP:' somewhere in the description.
Since jj moved to use git as a subprocess by default a couple versions
ago, they now deprecated the git.subprocess configuration option (jj
version 0.29). This commit removes it.
Can show tasks accomplished today (tdd, 'Task Done toDay'), since
yesterday (tdy, 'Task Done since Yesterday'), or in the last week (tdw,
'Task Done in the Week').
Taskwarrior hooks are removed from this general dotfiles repo, as they
are instead included in my taskwarrior 'task' folder (and project)
itself. Each hook belongs to exactly one taskwarrior repository and thus
they should also exist there and not anywhere else, is my current
opinion.
This is especially so since I believe most people use exactly one
taskwarrior repository (me included). So for the moment it just makes
the most sense to have these two things live side-by-side instead of in
this more general configuration repository.
Since it is technically vim-internal (and relatively rarely used unless
to debug things), I have moved the shortcut for this function from
`<leader>sh` (show-history) to `<leader>vp` (vim-print-messages).
The 'p'-suffix is a little unfortunate but currently h/H/m are all taken
in this vim-internal submenu.
The reasoning behind this is that the 'show' menu is intended primarily
for user-facing, middle-of-work tasks and windows that help me
accomplish goals when actually working and getting things done.
Showing the fidget history does not do that, but allows
introspection into the vim editor history. So, it should accordingly
live under the 'vim' menu. Additionally, it frees space in the
'show' menu and lets me/the user forget about the functionality
until it is needed.
Allows quickly listing and working with taskwarrior tasks from within
neovim. Show a floating `:NeoWarriorOpen` window with `<leader>sw` or a
vertical neowarrior buffer with `<leader>sW`.
We are using chafa to preview the image and video files but would always
default to the iterm implementation. This has been removed: The foot
terminal does not support iTerm and hard-coding makes us too tightly
coupled to wezterm. But even wezterm functions well with chafa without
the forced iterm usage - we simply use sixels instead.
Remove video preview frame hard-coded file caching and instead pipe
directly into chafa preview.
Though ostensibly compatible with typst, there is a show-stopping issue
with the main image.nvim fork which means an error message whenever
there is more than one typst buffer open (e.g. two side-by-side, or
opening a fzf-lua windows with typst previews, and so on).
Until that is fixed, use this fork. Issue here: https://github.com/3rd/image.nvim/pull/280
Dotlink now takes arbitrary arguments which it all simply passes through
to dotter underneath.
Also made the directory changing a little more flexible.
We add an additional 'core' user service (i.e. one that gets loaded
before all others by turnstile) which populates the TURNSTILE_ENV_DIR
with all manner of custom set env vars that are important for other
applications.
Most importantly, this sets up the XDG directory compliance for
applications either managed by turnstile or applications started through
turnstile on my system. So, for example `pass` knows to search for its
database in `XDG_DATA_HOME` and river knows to search for binaries in a
PATH which has been prefixed with my custom user binary location.
Everything is working well again with newer versions of blink-cmp. And
the development velocity is crazy, we are already two major versions
ahead. Some breaking changes but seemingly nothing that my relatively
simple configuration is affected by.
Remove most of the old cruft that was left over from nushell version
0.87 - we are now on version 0.102!
Many of the old options are actually not helpful anymore so let's just
get rid of them entirely (never configured the shell for me too much).
Also there was a lot of 'default' commented code which made it harder to
keep an overview rather than help.
For now just set up a minimal shell experience with vi editing mode, and
the trifecta of startship prompt, zoxide movement and atuin history
enabled.
All additional languages features (LSPs, treesitter parsers, linters and
formatters) are now defined in a single place in 'core/languages'.
This file simply sets up a big table which contains all the enabled
programs and parsers, divided by type. They adhere to the structure
given by the respective plugin.
HACK: We are still cheating a bit currently for treesitter parsers since
I have not had the heart to go through all of them to
activate/deactivate what I could need. Most of them are simply still
loaded, not connected to a specific language. Will have to be sorted out
at some point but it is good enough for now.
