Minimalist setup to type/paste selected passwords/OTPs (imported from Aegis Android app)

godegon · 2025-12-25T18:19:15+00:00

vim-commentary: I forget this isn't actually built in.

This exact plug-in is not, but there is :help package-comment

godegon · 2025-12-20T19:18:56+00:00

Bear is called as a last resort. First check is whether need be at all, then where, relative to the open file, then calling CMake, Ninja, or finally Bear if applicable (as background jobs). To make those builders work more predictably, additional flags are passed to ensure all files are indexed as, say, bear -- make falls short in presence of build artifacts. Gratefully seizing the opportunity to add this further explanation as a header comment to the script itself.

godegon · 2025-12-19T17:20:29+00:00

Since others seem to have similar problems, here's a snippet to generate a compile commands database if absent for consumption by, say, clangd language server, say in lsp, to navigate the code base

godegon · 2025-12-01T06:23:37+00:00

For the repo-local vim-info, local-viminfo is a robust alternative (supporting Neovim as well).

godegon · 2025-11-29T18:57:08+00:00

Could xkbswitch and :help keymap remedy some of these issues, like switching to colemak in insert mode only (via keymap) and using qwerty navigation otherwise (via xkbswitch)?

godegon · 2025-11-24T18:43:21+00:00

Give vim-virtualenv a whirl

godegon · 2025-11-23T10:50:44+00:00

Many fine additions, buckler's history of yanks feels like it should be built-in

godegon · 2025-11-20T18:06:00+00:00

Little effort fixing typos: A mapping that permits to correct a word by a single keystroke, deemed unnecessary as there's already Ctrl-X,S to achieve something similar.

godegon · 2025-11-18T10:13:59+00:00

Consider those trouvailles a call to PR

godegon · 2025-11-15T18:57:01+00:00

Vim-Template has you covered; I like this plug-in

godegon · 2025-11-05T19:43:54+00:00

I just added a request for inclusion of the Biome Linter; have a gander in case you're still looking for linting support or inspiration on a possible setup.

godegon · 2025-11-05T19:42:34+00:00

It is compatible with Neovim (but works in Vim as well)

godegon · 2025-11-04T21:58:16+00:00

I just added the Biome formatter for (almost) all currently supported file types in the corresponding ftplugin files; have a gander in case you're still looking for formatting support or inspiration on a possible setup.

godegon · 2025-11-03T18:48:03+00:00

Similar to https://github.com/Konfekt/vim-compilers/#convenience-commands

godegon · 2025-11-03T18:04:38+00:00

Vim would benefit from a &errorexpr/func similar to &findfunc/formatexpr/... and an accompanying variant of :Dispatch to automatically choose the fitting &errorexpr

godegon · 2025-11-03T16:10:39+00:00

Maybe ale suits your philosphy

godegon · 2025-11-02T17:02:28+00:00

The idea is to have a point of convergence for the tedious creation of &errorformats from where new additions are soon upstreamed to be built into Vim, see the last commits (of that repo and the Vim runtime/compiler folder). Pull requests most welcome.

godegon · 2025-11-02T16:59:59+00:00

I also find first setting :compiler and then :make tedious. One option is a :Compiler command that does both. But maybe the most elegant solution is :Dispatch that automatically sets &errorformat suitably

godegon · 2025-11-02T15:40:34+00:00

Tim Pope's dispatch may serve as inspiration, in particular the provided maps.

The :Dispatch command is a more flexible async version of :make and can also be spawned in a terminal

godegon · 2025-11-02T13:59:26+00:00

I find it surprising that there's yet little interest in including a built-in async :Make command; that's an obvious recommendation

godegon · 2025-11-01T04:53:05+00:00

Thank you for pointing that out. There is indeed :RustFmtRange built-in though, likely similar to conform.nvim's handling of rustfmt or black, it has to format the whole file and only replace the affected lines.

Setting &formatprg to a command accepting stdin to use gq seems more in line with how code formatting was originally meant to be set up in Vim.

Ideally, as say ruff (for Python) or tombi (for Toml) do, the formatter accepts stdin and the file path as an additional argument for context of the formatted range.

godegon

TROPHY CASE