asyncrun.vim VS vim-dispatch

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:

Tis is good for the compilation to make it async( otherwise it blocks) https://github.com/tpope/vim-dispatch it wraps around the built in make/makeprg feature. Would recommend that you dont do it with large builds/outputs.

vim-dispatch by the legend Tim Pope. send the task to the background, keep using editor. once the task is finished, it output to qflist buffer

The other answer here covers everything you need, but if you want a plugin-based solution you might be interested in vim-dispatch which runs command line tools asynchronously, and offers the option to run the command in the background instead with :Dispatch!.

You should check :h compiler :h make and :h 'errorformat'. You could also check vim dispatch, a plugin that enhances this features

Also plugin supports asynchronous execution (using terminal, jobs or vim-dispatch).

Do note that :make is blocking, and you need to wait until it finishes before it sends you back to the editor. If you want it to be asynchronouns, you can install vim-dispatch + vim-dispatch-neovim for Neovim support in vim-dispatch.

if you want something to work out of the box, is async and is already configured per language, check out TPope's dispatch

For long-running programs, like compiling, or running full test suites, or running terraform on a decently sized infrastructure project, I may run them with :Make (courtesy of tpope/vim-dispatch) so I can keep working on the project while the external program is running. If I'm in an environment without vim plugins, I may spawn a new tmux pane/window. As a last resort, I will ctrl-z/fg if I don't have tmux on the remote system (e.g. dev containers).