AsyncRun.vim VS Atom-IDE

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

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). Source: about 1 year ago

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. Source: about 1 year ago

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. Source: over 1 year ago

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). Source: over 1 year ago

Not a stupid question at all! It is just a code editor. They do have an IDE for compiling ( https://ide.atom.io ) but I haven’t used it so I’m not sure about it’s capabilities. Source: almost 2 years ago

Gotcha! Although it’s no longer maintained, I’ve had no issues with the Atom IDE package. It contains a lot of the same features that you’d expect like code completion, code linting to check for errors before you compile, and the ability to build and run from the Atom editor. Source: over 2 years ago