vim-build-tools-wrapper VS asyncrun.vim

PS: here is an old screencast from the time I had a single global queue for everything: https://github.com/LucHermitte/vim-build-tools-wrapper/blob/project/doc/make_run.md#demo

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: