lazy-require.nvim
toggleterm.nvim
lazy-require.nvim | toggleterm.nvim | |
---|---|---|
4 | 89 | |
112 | 3,732 | |
- | - | |
0.0 | 8.2 | |
over 1 year ago | 12 days ago | |
Lua | Lua | |
MIT License | 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.
lazy-require.nvim
-
Best way to lazy load plugin on keys that include a require() call?
Normally you can use tjdevries/lazy-require.nvim/ but sadly neotest's function is hidden under 2-depth table.
-
lazy.nvim: a new plugin manager for Neovim
But FYI, there might be a name clash with https://github.com/tjdevries/lazy.nvim :-/
-
What do you want to know about the process of converting an init.vim to init.lua setup?
Here is my understanding. There is a penalty for using vim.cmd or accessing vim functions. They supposedly will only run as fast as they would in vimscript it's self so not very fast. Not sure of any of them are actually functioning different from their vimscript implementation. Vim.cmd likely is even slower since it requires the extra overhead of persing the vimscript. For lazy loading take a look at https://github.com/tjdevries/lazy.nvim .
- A small trick to improve your init.lua startuptimes
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?
nvim-conf - ☄ Maddison's Neovim configuration!
vim-floaterm - :computer: Terminal manager for (neo)vim
nest.nvim
neoterm - Wrapper of some vim/neovim's :terminal functions.
neovim - Vim-fork focused on extensibility and usability
multiterm.vim - Toggle and Switch Between Multiple Floating Terminals in NeoVim or Vim
dotfiles
AstroNvim - AstroNvim is an aesthetic and feature-rich neovim config that is extensible and easy to use with a great set of plugins
dotfiles
tmux - tmux source code
dotfiles - my settings
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]