I'm using neovim. When I visually select a comment in Python that is longer than my textwidth setting, and press gq, it does not wrap the comment.
I've looked at this question: visual mode gq not reflowing comment block, however my formatoptions setting looks correct:
set formatoptions=cjoqrt
What is causing this to not work?
As mentioned by @cassava, your problem may be due to this PR, which changes formatexpr to take its initial value from the LSP (as I understand it).
There are a few suggestions for workarounds in this issue, linked to from this Reddit thread, of which using gw instead of gq seems like the easiest one-off workaround, and this snippet works for me for a more robust approach:
-- Use internal formatting for bindings like gq.
vim.api.nvim_create_autocmd('LspAttach', {
callback = function(args)
vim.bo[args.buf].formatexpr = nil
end,
})
Alternatively, I am using the below to restore the prior behavior specifically for Python / pylsp:
local pylsp_on_attach = function(client, bufnr)
default_lsp_on_attach(client, bufnr)
-- Restore gqq
vim.api.nvim_buf_set_option(bufnr, "formatexpr", "")
end
nvim_lsp.pylsp.setup({
-- ...
on_attach = pylsp_on_attach,
-- ...
})
:gw was thing (:gq was baked into my brain for years). That worked for me!
Commented
Jan 20, 2023 at 22:26
:gw doesn't work for me either. @n8henrie do you mind adding some comments around what each of the two snippets you've listed actually does and why they fix the underlying issue? The first one reads like it just disables using LSP for formatting to restore :gq behavior. Is that correct?
Commented
Jun 2, 2023 at 23:37
formatexpris set tov:lua.vim.lsp.formatexpr(). This makes Neovim use a language server to format, also withgq. I don't how how to preserve that and also be able to wrap text withgq. You can:set formatexpr=to just get the wrapping.:set formatexpr=madegqwork again. Although I'm curious, what else might I be losing by un-settingformatexpr?:set formatexpr=.