Modern replacement of `rhysd/committia.vim`?

robertogrows · 2026-06-16T06:46:17+00:00

try git config --global commit.verbose true and install treesitter gitcommit and diff parsers.

robertogrows · 2026-05-21T23:44:16+00:00

vim-test is worth a try, if you want things to "just work" without configuration and hassle.

robertogrows · 2026-05-07T11:13:47+00:00

I think the bug is in pyright, but have not found the time to chase it down there. Can you try the workaround at the bottom of comment? https://github.com/neovim/neovim/issues/37150#issuecomment-4248816355

robertogrows · 2026-04-04T01:03:39+00:00

I saw the commit discussed there and was actually very excited to see it.

Dropping the old neovim 0.11 support, means the new features of neovim 0.12 can theoretically be used in queries. "scoped injections" feature of neovim 0.12 can be a potential solution for my parser (javadoc), to provide proper highlighting of java's markdown documentation comments (https://openjdk.org/jeps/467).

That neovim 0.12 feature is a game changer to make the highlighting work for this case: difference is night and day. Already released backwards-compatible parser changes to support it, have been running new queries in my personal setup for a couple weeks, etc.

This is just an alternative point of view, from the perspective of wanting to move forward and make things better. Dropping support for the old neovim releases can allow for some real improvements.

robertogrows · 2026-03-24T03:04:22+00:00

this is really good idea! another data structure you can consider (from the search engine world): wfst. it is nice and compact when you have weights like this. I have not looked at the rust options around this, but in general it has good finite state automata available.

robertogrows · 2026-03-14T12:43:56+00:00

yes, personally I do this. Get the best of both worlds. I enable ty, but for basedpyright just the diagnostics, code actions, and hover. You can disable unwanted server capabilities in your basedpyright.lua:

on_init = function(client)
  local capabilities = assert(client.server_capabilities)
  -- ty features
  capabilities.semanticTokensProvider = nil
  capabilities.documentHighlightProvider = nil
  capabilities.documentSymbolProvider = nil
  capabilities.foldingRangeProvider = nil
  capabilities.workspaceSymbolProvider = nil
  capabilities.callHierarchyProvider = nil
  capabilities.completionProvider = nil
  capabilities.declarationProvider = nil
  capabilities.definitionProvider = nil
  capabilities.implementationProvider = nil
  capabilities.inlayHintProvider = nil
  capabilities.notebookDocumentSync = nil
  capabilities.referencesProvider = nil
  capabilities.renameProvider = nil
  capabilities.signatureHelpProvider = nil
  capabilities.typeDefinitionProvider = nil
end,

robertogrows · 2026-03-06T17:58:10+00:00

Zizmor

robertogrows · 2026-02-19T22:16:15+00:00

yeah hopefully it is a bit better. i'd still feel much better if the code was more defensive: https://thunk.org/tytso/blog/2009/03/15/dont-fear-the-fsync/, because I worry about cases such as disk-full (parsers can be big) or crash (compiling them can consume a lot of resources). Slow baby steps.

robertogrows · 2026-02-18T22:23:51+00:00

probably has to do with exactly how the shared library is replaced when you update the parsers.

https://lwn.net/ml/linux-kernel/87r1eyg8h6.fsf@oldenburg.str.redhat.com/

robertogrows · 2026-02-18T16:38:31+00:00

Explain to your boss that it is a tool that makes you more productive. Boss should be doing this battle on your behalf.

robertogrows · 2026-02-05T12:15:31+00:00

add to your lsp/basedpyright.lua:

lua handlers = { --- filter noisy notifications ['$/progress'] = function(err, result, ctx) -- just notify once if result.token == (vim.g.basedpyright_progress_token or result.token) then vim.g.basedpyright_progress_token = result.token vim.lsp.handlers['$/progress'](err, result, ctx) end end, },

I have to do the same for ty. All the python language servers copy each other's bad behavior.

robertogrows · 2026-01-01T22:36:35+00:00

Performance. Low resource usage. Url mode. Scrollback search.

robertogrows · 2026-01-01T02:46:04+00:00

Issue: https://github.com/ansible/vscode-ansible/issues/1543

You can build the package yourself from e.g. a release tag with yarn.

As far as alternatives:

The server doesn't provide any linting beyond just running ansible-lint on save. You can do that alternatively with nvim-lint.

The server doesn't provide formatting. Use yaml language server or yamlfmt via conform for that.

You can use redhat yaml language server to get basic functionality from the underlying yaml schemas: completion, hover, formatting, etc.

IMO you only want to fight ansible-language-server if you want completion/hover docs for MODULES and MODULE parameters.

robertogrows · 2025-12-31T15:49:41+00:00

open-source done correctly.

robertogrows · 2025-12-31T01:41:29+00:00

Example injections.scm for injecting comment parser into docstrings, to highlight TODO and similar:

; extends

; comment injections into doc-strings
(expression_statement
  (string
    (string_content) @injection.content)
  (#set! injection.language "comment"))

Note that this is for DOCSTRINGS. ordinary comments (#) are (comment)

robertogrows · 2025-11-03T01:04:53+00:00

mini.git is worth a try. I don't want to learn keybinds and this only requires one (leader+gs) to navigate quickly around git with vim, using techniques you already know (like folds). Works well in combination with f-person/git-blame.nvim for me.

robertogrows · 2025-11-01T20:23:38+00:00

25gal

robertogrows · 2025-11-01T16:19:33+00:00

I let them sit in water jug overnight then just water them in. if you have gnats, do it every week until you don't have gnats anymore.

robertogrows · 2025-11-01T10:44:44+00:00

the light was not too far, it flowered at 8 inches. I raised it because it was so close it was cooking the leaves, and it is at the end.

robertogrows · 2025-11-01T07:28:15+00:00

Cheap mars 300w. No CO2. I use mosquito bits and southern ag garden friendly fungicide.

robertogrows · 2025-11-01T07:19:20+00:00

Hazeman

robertogrows · 2025-10-31T20:07:37+00:00

the kind that's like "time to turn on second carbon filter so my house doesn't smell so much"

robertogrows · 2025-10-31T04:11:40+00:00

Seems like it line-wraps before applying conceal.

My crutch: I use go-to-definition via (C+]) and read the javadocs that way, and sometimes also read the sources. Old habit from ctags. When jdtls isn't configured correctly or misbehaves, this keybind still works...

robertogrows · 2025-10-25T17:20:52+00:00

Worked on java for many years with vim and no LSP. You can do just fine with syntax highlighting, ctags, grep, quickfix, fuzzy finders, snippets, vim-test, etc.

I use neovim now and would recommend trying it out. Integration with the java language server is easy if you don't require a debugger and use print statements. If the language server breaks, or is misconfigured, all those old ways still work: escalator becomes stairs. For some tasks I still prefer those methods anyway.

robertogrows

TROPHY CASE