consolation.nvim VS yabs.nvim

You might like https://github.com/pianocomposer321/consolation.nvim

I wrote two plugins for exactly this purpose. One is pianocomposer321/yabs.nvim, which allows you to specify which commands (vim ex commands, or external commands) should be run for which filetype, and also where the output should go (the quickfix list, the terminal, etc). The other is pianocomposer321/consolation.nvim, which allows for easy management of terminals. These plugins will work independently of each other, but they work best together.

toggletasks.nvim is a task manager inspired by yabs.nvim and projectlaunch.nvim. In fact initially I wanted to extend projectlaunch.nvim, but then I decided that I want to make too many changes and it should be a separate plugin. A small comparison is in the README.

Or maybe this: https://github.com/pianocomposer321/yabs.nvim

I'm the author of https://github.com/pianocomposer321/yabs.nvim. I've been thinking for a while that it might be time for either a major refactor or a complete rewrite, and this last week I decided to just do it. I won't get into all the reasons why I thought this was a good choice (if y'all want to hear why, I'll probably explain in a separate post when I announce that the new version is done), but my question is this: when I'm ready to put the new version up on github, should it be in a new repository under a new name, or under a new branch in the current version? It seems that most other people have always done it under a new repository, but then I'd have to come up with a new name (😬), and it wouldn't have the same discoverability as the original repo did, at least at first (because it would start with no stars). On the other hand, if I made it just a new branch, I'd have to add a deprecation message to the current main branch saying that the new version will eventually take it's place, and that will be a small but annoying breaking change for existing users who don't want to switch to the new version.

I haven't tried it myself yet but perhaps yabs.nvim is what you're looking for?

I current use yabs.nvim, which is very similar to what you're trying to do.

I would like to setup tasks with YABS that are opened inside a ToggleTerm floating terminal window.

Hello everyone, I'm the author of yabs.nvim. For those of you who don't know, yabs adds functionality similar to vscode's tasks system to neovim. In any case, we recently passed 100 stars on github, and this milestone seemed like an appropriate time to thank everyone who's helped get to that point.

I wrote two plugins for exactly this purpose. One is pianocomposer321/yabs.nvim, which allows you to specify which commands (vim ex commands, or external commands) should be run for which filetype, and also where the output should go (the quickfix list, the terminal, etc). The other is pianocomposer321/consolation.nvim, which allows for easy management of terminals. These plugins will work independently of each other, but they work best together.