yabs.nvim
projectlaunch.nvim
yabs.nvim | projectlaunch.nvim | |
---|---|---|
12 | 3 | |
202 | 33 | |
- | - | |
0.0 | 4.8 | |
4 months ago | 6 months ago | |
Lua | Lua | |
GNU Affero General Public License v3.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
yabs.nvim
-
toggletasks.nvim - toggleterm+telescope task runner with JSON/YAML configs
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.
-
Any plugins for project local building and makeprg?
Or maybe this: https://github.com/pianocomposer321/yabs.nvim
-
Should a plugin rewrite be a new repository, or a new branch on the existing one?
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.
- How to compile and execute C++ cmake, make?
-
How do I compile and run Java with NeoVim? (for learning Java)
I haven't tried it myself yet but perhaps yabs.nvim is what you're looking for?
-
[Plugin] BuildTask.nvim: Run tasks similar to VScode
I current use yabs.nvim, which is very similar to what you're trying to do.
-
ToggleTerm with YABS
I would like to setup tasks with YABS that are opened inside a ToggleTerm floating terminal window.
-
Thanks everyone! (Yabs.nvim makes it to 100 stars!)
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.
- yabs.nvim - Yet another build system for neovim, written in lua
-
How to run C++ from vim in an external terminal window with ability to add input.
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.
projectlaunch.nvim
-
toggletasks.nvim - toggleterm+telescope task runner with JSON/YAML configs
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.
-
possession.nvim: flexible & extensible session management
Additional functionality is provided by plugins that run on save/load hooks. Currently available plugins allow to close windows / hidden buffers and there's a plugin for storing/restoring nvim-tree explorer windows. Some future ideas could be integrating with things like projectlaunch.nvim to automatically start/stop jobs when changing sessions. The core architecture for adding new plugins is already there so it should be pretty easy to add new ones.
-
Projectlaunch.nvim - a plugin I made for launching commands in projects in floating or split windows
Projectlaunch.nvim (requires a pretty new version of Neovim 0.7.0 for Lua autocmd support). There's a demo video in the repo's readme!
What are some alternatives?
code_runner.nvim - Neovim plugin.The best code runner you could have, it is like the one in vscode but with super powers, it manages projects like in intellij but without being slow
possession.nvim - Flexible session management for Neovim.
vim-dispatch - dispatch.vim: Asynchronous build and test dispatcher
toggletasks.nvim - Neovim task runner: JSON/YAML + toggleterm.nvim + telescope.nvim
neovim-java - Neovim Java client library. Provides multiple interfaces for communicating with Neovim instance via multiple different protocols. - Moved to https://codeberg.org/neovim-java/neovim-java
nvim-tree.lua - A file explorer tree for neovim written in lua
asynctasks.vim - :rocket: Modern Task System for Project Building, Testing and Deploying !!
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
consolation.nvim - A general-purpose terminal wrapper and management plugin for neovim, written in lua
neovim-cmake - CMake integration for Neovim
dotfiles - dotfiles for phyOS base, status bar scripts & lua nvim config