asyncrun.vim VS overseer.nvim

I'm familiar with asyncrun.vim, but it outputs as quickfix. I specifically want to filter editor text (as stdin/stdout).

If you want to open a new terminal in the CWD of neovim, you couls either use neovim's built in terminal or, if it needa to be kitty, use the neovim AsyncRun-plugin and start kitty with the necessary command-line options to start in neovims's CWD(I uae this with Alacritty instead of Kitty).

For running the file there are several tools. I have been using asynctasks.vim which is built on top of asyncrun.vim which I usually use to open a tmux pane and run the code/test. I've been looking at switching to overseer.nvim but haven't yet. I use justfiles to define all of my tasks.

I can :Man blah to look up docs or :AsyncRun to build/run with jumpable output in the quickfix. Doing it within vim means I can pull from any register for pasting, yank without a mouse, hide buffers or move them to tabs, etc.

I use asyncrun.vim to see compile output as it happens (line by line instead of the whole dump when compile completes) and asynchronously (so I can keep navigating around).

try asyncrun:

Also AsyncRun and AsyncTasks worth a mention.

Hey folks, I'm using asyncrun to run async commands on vim, but some of them output ansi colorcodes, I've found powerman's AnsiEsc which is able to conceal and highlight them very well, but that only work for the current buffer, so there's no way to automate it from g:asyncrun_exit and I can't set the -post from asynctasks, has anyone found a way to fix this?

As you can see, I use asyncrun.nvim since sometime compiling/running will take quite long. For some complex situations, like c++ project with cmake, I use following code:

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