neotest VS overseer.nvim

My first neovim plugin project was to write an adapter (runner) for neotest, for a language that I use regularly and which was missing from the existing adapters.

There's overseer.nvim to run all sorts of things and neotest to run tests. In general, you can check awesome-neovim or TWiN to look for plugins.

Here's some things that may help: - https://github.com/mfussenegger/nvim-dap + dap ui - https://github.com/nvim-neotest/neotest

I use neotest to run tests (with pytest).

For testing I use https://github.com/nvim-neotest/neotest which gives a nice outline.

For those who don't know it, it's an adapter for neotest, a Neovim plugin that

You might look at how Neotest handles this, or even see if you can use/contribute to that project directly. It already has support for a fair number of languages at varying levels of maturity.

I am writing Python these days, and LSP + DAP + neotest give me 90% of what PyCharm would have given me. I don't know how well this works with Java, the latter two did not exist when I was still writing Java. The way I did it was use Neovim with jdt-ls to write code and IntelliJ for debugging. Debugging does not require switching between keyboard and mouse, so it was OK to me.

I'm sure that we could figure out a way to install rocks without luarocks, but it's still going to be an additional step with possible complications. Personally, I would rather just embed the library within my plugin like neotest does with xml2lua. The marginal cost of a slightly larger install is more than paid for by an easier install process and a guarantee that it works.

When working on multiple projects it might be useful to define some local configuration that should be automatically loaded. This e.g. includes customized LSP configuration or adding build tasks for task runner plugins like overseer.nvim. To do that you can create .nvim.lua in your project directory and define your local settings there.

I use https://github.com/stevearc/overseer.nvim, a task/job runner kinda like the one in VS Code. You can run your builds, tests, lints, etc. with it.

overseer.nvim

There's overseer.nvim to run all sorts of things and neotest to run tests. In general, you can check awesome-neovim or TWiN to look for plugins.

Here's an example of how to configure your vim_ui_select picker for the amazing task managing plugin overseer.nvim!

I use overseer for this https://github.com/stevearc/overseer.nvim

I would like to call out that "make compiler plugins async" sounds like a simple change, but quickly becomes quite complex. Let's say you do an async :make, now you have a background process. How do you cancel it? How do you view the output? Can you hide it and then come back to it? Can you run more than one at a time? Can you view all running tasks? If you want to have only very basic controls you could do what vim-dispatch is doing, but I personally don't think it's very good. I think any solution shy of VS Code style tasks control will be insufficient, but I think the appetite for adding something that complex to core Neovim is quite low. That said, this (and more) is something I really wanted, which is why I wrote overseer.nvim

I still can't get testing and debugging tests down, so I am going back to intellij or goland to do that. I have been at it for about 3 weeks now. I spent so much time setting up my config. haha. Having said that, I really like Overseer https://github.com/stevearc/overseer.nvim

overseer.nvim