null-ls attaches to every buffer about null-ls.nvim HOT 5 CLOSED

@jose-elias-alvarez you're right, disable gitsigns works.

I enable gitsigns' code action because I'm curious what it provides, I don't actually use it so disabling it is fine for me.

Thanks for the quick help and great plugin, it's faster than efm and easier to config IMO, hope it will get more mature in the future.

from null-ls.nvim.

Hey! You're right about the expected behavior, and in fact I pushed a commit in the past couple of days that solved an issue causing null-ls to attach to all buffers. Are you still seeing this behavior on the latest commit?

from null-ls.nvim.

Sorry, forgot to close this one. Works as expected! Thanks!

from null-ls.nvim.

hi @jose-elias-alvarez, I'm getting the same issue, I'm using dartls (akinsho/flutter-tools)

I have this autocmd to run format on save when in dart buffer:

autocmd BufWritePre *.dart lua vim.lsp.buf.formatting_sync({}, 200)

Every time I save a dart buffer, neovim prompts me to choose between dartls and null-ls.

I also see null-ls in :LspInfo output.

How do I make null-ls ignore every filetype but the ones in the null-ls configuration?

My null-ls config:

local null_ls = require("null-ls")
local sources = {
	null_ls.builtins.formatting.stylua,
	null_ls.builtins.code_actions.gitsigns,
}
null_ls.setup({ sources = sources })

I also use your nvim-lsp-ts-utils plugin to integrate eslint and prettierd with null-ls.

from null-ls.nvim.

@nghialm269 Judging from your config, your issue is actually a bit different – it's because the Gitsigns builtin is enabled for all filetypes by default, and null-ls currently cannot recognize that it's not able to respond to the formatting request. This is something I want to work on when I have a little time, though, so I've opened up #28.

Edit: a (lousy) workaround for now is to specifically define the filetypes you want to use with Gitsigns:

null_ls.builtins.code_actions.gitsigns.with({ filetypes = { ... } })

Not a great workaround, though, and if I'm not wrong it shouldn't be too hard to fix it at the plugin level without workarounds, so keep an eye on the issue.

from null-ls.nvim.