yabs.nvim
toggleterm.nvim
yabs.nvim | toggleterm.nvim | |
---|---|---|
12 | 89 | |
202 | 3,764 | |
- | - | |
0.0 | 8.2 | |
4 months ago | 22 days ago | |
Lua | Lua | |
GNU Affero General Public License v3.0 | GNU General Public License v3.0 only |
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.
toggleterm.nvim
-
Neovide – a simple, no-nonsense, cross-platform GUI for Neovim
As a data point, I'd like to chime in here. I have been a 15 year user of tmux (and screen before that) and never thought I'd change my development habits. Over the holidays I decided I would do one of those once-every-five-years upgrades to my vim setup as I had accrued dozens of vendored plugins in normal vim and wanted to see what the big deal with neovim was.
I bit the bullet and evaluated some of the "distributions" (AstroNvim and kickstarter) and played around with all the new lua plugins that I had never thought I needed (why use telescope when FZF-vim worked so well?).
Anyways, after a month of tweaking and absorbing, I found myself running Neovide only, and doing something I never thought I'd see, running tmux from within neovim/neovide. I think this only works (for me) because of session management (there are half a dozen plugins for handling quickly changing 'workspaces') and because the built-in terminal (with a very useful plugin called toggleterm: https://github.com/akinsho/toggleterm.nvim) works so well.
I have not stopped using tmux and layouts, and it sits in another fullscreen iterm2 workspace, but I find that I now spend 90% of my time using a fullscreen neovide and summoning/toggling tmux momentarily for running commands.
Of course, the caveat here is that my preferred mode of operation is being fullscreen as often as possible. I think if your preferred mode of operation is to always see splits then running neovim from the terminal within tmux is still the way to go.
As for why I like neovide? I find the animations, when tweaked to be less 'cool' are extremely useful to see where the cursor jumps to. I am also a huge fan of the fact that I can finally use 'linespace' to put some space between my lines of code -- it is an aesthetic I didn't realize I wanted.
-
NeoVim Capability Functions
For splitting the terminal you could try either toggleterm or tmux. If you want to send things from one tmux pane to another, then you can use slime. For a toggle-able filetree, you can use nvim tree.
-
Is there any gotchas for using Neovim's built in terminal?
I just found toggleterm which feels awesome. Pretty much exactly what I was looking for to use with Alacritty but even better since its integrated into the rest of my Neovim workflow.
-
How to unfloat a terminal in Lazyvim
I saw this plugin that tells me how to do it, however I got confused after I added "require("toggleterm").setup({})" in the lazy.lua file and installed the package as well using the Lazy command
-
VSCode-like terminal setup
I tried toggleterm but I wasn't successful.
-
Noobie Needs a Nudge
And I never really got into Gitsigns or vim-fugitive. Lots of people love them, so I'm sure they're great, but I'm happy opening a floating terminal with Toggleterm and using Lazygit.
-
Using Floaterm, what's the best way to toggle between the editor and opened window and maintain the shell session?
I agree with u/Bamseg, but you can get what you want using toggleterm.nvim BUT NOT IN FLOAT.
-
What do you use for git integration in neovim?
I use gitsigns for linewise operations (blame, reset, etc), and a floating terminal (toggleterm) for everything else. flatten.nvim also helps with nested nvim instances.
-
Switching from Emacs. My experience
but I ended up finding a good enough workaround by using Lazygit through Toggleterm.
-
Just got neovim up and working
Perhaps you want something like https://github.com/akinsho/toggleterm.nvim and make a custom profile? Remapping a key for each extension seems fine as well, just remap it per-buffer inside of on_attach
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
vim-floaterm - :computer: Terminal manager for (neo)vim
vim-dispatch - dispatch.vim: Asynchronous build and test dispatcher
neoterm - Wrapper of some vim/neovim's :terminal functions.
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
multiterm.vim - Toggle and Switch Between Multiple Floating Terminals in NeoVim or Vim
asynctasks.vim - :rocket: Modern Task System for Project Building, Testing and Deploying !!
AstroNvim - AstroNvim is an aesthetic and feature-rich neovim config that is extensible and easy to use with a great set of plugins
consolation.nvim - A general-purpose terminal wrapper and management plugin for neovim, written in lua
tmux - tmux source code
toggletasks.nvim - Neovim task runner: JSON/YAML + toggleterm.nvim + telescope.nvim
AstroVim - AstroNvim is an aesthetic and feature-rich neovim config that is extensible and easy to use with a great set of plugins [Moved to: https://github.com/AstroNvim/AstroNvim]