dotfiles VS nvim-lint

Didn't think I'll see another user with a similar config than mine. I also use ALE + nvim-lsp + ddc. So you can have a look at my config and feel free to DM me with your concerns.

My nightly config with ddc in lua

Also here is my galaxyline code if you want to take a look at it: https://github.com/creativenull/dotfiles/blob/8d1840a30265963aef71458363ccd621969b86b2/.config/nvim-nightly/lua/cnull/statusline.lua

But since you are in lua you will have to evaluate the lua inside vim which is then passed on as a string (kinda complicated to explain, code is a bit clearer), I did something similar with my status line, although a bit more minimal which you can take a look at it here.

I'm not sure what issues you're having with it, it should run all the linters and fixers automatically without any configuration needed to add in your config, besides adding the plugin. :ALEInfo is a great place to look at to see whats enabled and working. I like a bit control so i disable the automatic running and turn on only the linter/formatter I need on a filetype basis (aka add then to after/ftplugin), you can take a look at my dotfiles and see how I have them setup.

I've had the same issue, I just had to change the find_command key in the find_files function on telescope and create a different keymap to call it, you can take a look at my telescope setup

So what you really want, is to merge those two tables together, you can have a look at how I do it in my nvim lsp config but for your code it could be:

Personally, i think nvim-lint is the best alternative currently, specially so because it has no dependencies on external binaries. This guide assumes you already have your LSP set up with nvim-lspconfig (or an alternative like lsp-zero). You should also have an way to install the linters you are gonna need, i highly recommend Mason with mason-lspconfig.

Try out https://github.com/mfussenegger/nvim-lint for linting tools, it integrates with nvim diagnostics module, might cover all use cases of null-ls for someone shopping around.

People looking for alternative can check these projects: - nvim-lint - formatter.nvim

For linting, I would recommend nvim-lint. Again the same step as before, a little bit of setup code to register your linter and you're good to go!

This will be the third linting solution to make use of the [Neovim Diagnostic] module after null-ls and nvim-lint. All can co-exist, all have the pros and cons.

I use nvim-lint (https://github.com/mfussenegger/nvim-lint), but I still don't know exactly how to achieve your goals with it. My hunch is that it should be somewhat straightforward, since Lua code could be used to provide the executable command (i.e. if in poetry project then cmd =poetry run ...else if ... then ... end)

It's not obvious from the website, but this is the blog of GitHub user @mfussenegger, who is a Neovim core member, one of the primary maintainers of Neovim's LSP client implementation, and the other of several excellent plugins.

https://github.com/mfussenegger/nvim-lint works with the diagnostics API that was created after LSP was added, to allow non-LSP to use diagnostics API. Meaning you can see LSP and linting in the same interfaces if you use this API.

As part of my work-in-progress Neovim [plugin]([https://github.com/nat-418/tcl.nvim)(https://github.com/nat-418/tcl.nvim)) for Tcl development, I added support for Nagelfar syntax checking in the nvim-lint plugin. This provides inline checking for errors as seen in the attached screenshot. If anyone has any ideas on how to create a Tcl Language Server, or knows of a project already working on one, I would be very interested to know about it.