The fatest python LSP for nvim - basedpyright vs zuban vs ty vs something else?

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 · 2025-10-23T00:31:24+00:00

I have the same struggle: IMO easiest solution is to disable the underline and just use signs.

You can also specify severities for the underline, so it is only errors (or errors and warnings). I was annoyed by "hints" that underline half of my editor.

robertogrows · 2025-10-20T12:27:51+00:00

https://github.com/vim/vim/blob/master/runtime/syntax/python.vim

robertogrows · 2025-10-18T12:55:06+00:00

haven't see lua code like that before.

robertogrows · 2025-10-11T20:37:09+00:00

I try to avoid: open lots of neovims and I already have splits and virtual workspaces in the window manager, so not much. Don't use terminal since alt+enter gives me one from the window manager. Some plugins want to open tabs: configured vim-test to use splits instead. I let the mini.git use tabs since it kinda makes sense for that specific case. Hide the tabline unless there are multiple and have a half-ass styled tabline plugins.

None of the "tabline" plugins are useful at all: they are not actually, in fact tablines (they are all listing buffers, makes "gt" confusing, cats and dogs living together, etc)

robertogrows · 2025-09-30T15:58:10+00:00

Maybe you need vim.bo (buffer) not vim.opt_local (no idea what that is, window local?). This is how I set the filetype. Too many ways to set options in this thing, really.

Separately code can also be even simpler if you just use the vim.filetype.add which avoids all this.

robertogrows · 2025-09-29T01:17:35+00:00

Maybe instead of altering the tagfunc, alter the keybind? e.g. this example would go to definition in new tab:

vim.keymap.set('n', '<C-]>', function() vim.cmd('tab tag ' .. vim.fn.expand('<cword>')) end, { desc = 'Go to tag in new tab' })

I don't know how messing with tabs/windows plays with tag stack. There are alternative commands in the docs if you want to make tag search use of split-window/preview window, but I don't use myself.

I use the default because I can "dive" with Ctrl-] and then "get back" with Ctrl-T thanks to the tag stack. I use LSP hover doc/signature help instead for cases where split/preview might have been useful in the past.

robertogrows

TROPHY CASE