pact.nvim
๐ช๐ฉธ๐ semver aware package manager for neovim (by rktjmp)
leap.nvim
Neovim's answer to the mouse ๐ฆ (by ggandor)
pact.nvim | leap.nvim | |
---|---|---|
1 | 41 | |
43 | 3,968 | |
- | - | |
0.0 | 9.3 | |
over 1 year ago | 20 days ago | |
Fennel | Fennel | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
pact.nvim
Posts with mentions or reviews of pact.nvim.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-21.
-
Hibiscus ๐บ -- Fennel eye-candy for neovim
Macros are pretty attractive, because you suddenly feel really unconstrained by syntax. You can write a fennel macro to handle really weird non-uniform syntax which can be exciting. In the end, it's generally less hassle to go with functions though. Often I'll write a macro, then tune it, then tune it again, then realise I just need a function function, i.e this was all a macro initially but now the macro is simply sugar to let you go (await (my-func 10)), and even then it's pretty debatable if simply accepting a function name and arguments is particularly worse (i.e: (await my-func 10) where await is just a function), I really just wanted to retain the "call style" on the day I wrote it. They do give you a lot of power though, one of the first things I wrote after Hotpot was a macro to set keymaps to functions directly, with closure scope which would have been pretty annoying without the macro - possible as the macro is just lua in the end, but pretty annoying, annoying enough that most people didn't bind "one shot" functions. I think that is where macros really shine, allowing you to actually patch short comings, not just alter syntax. Apart from that - which is now deprecated by 0.7 - I think I have one other macro in my config which ... could actually just be a function.
leap.nvim
Posts with mentions or reviews of leap.nvim.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-21.
-
Your favourite Neovim plugins?
Also I really like leap.nvim which in my opinion is the best thought out "hop" variation.
-
This Week In Neovim #44 โ Mon May 29th 2023
Your plugins are great but I haven't tried mini.jump2d. However, compared to hop.nvim I prefer leap.nvim's jumping philosophy because it uses information you already have before starting the jump, and you just have to type one "virtual" character, which in my opinion is a smoother experience.
- Feeling super slow...
- leap.nvim meets vim-illuminate
-
Anyone know if there are plans to add leap.nvim behavior to helix?
Here's the repo if you haven't heard about it: https://github.com/ggandor/leap.nvim Otherwise, does anyone know if there are ways to emulate that behavior with existing keybings? And, if all else fails, would you like to see it as a feature request?
-
People who migrated from vscode
leap.nvim absolutely turned my movements and navigation experience in neovim upside down.
- What do you use 's' for in normal mode? vanilla? or something like leap?
-
Iโm a vscode user who wants to migrate to neovim but still canโt get all the features I want, Iโm trying out lazyvim, which plug-ins should I use?
I like Leap
-
How come NeoVim, with all the "API is first-class" and "extensibility" brags, has such bad documentation on these topics compared to Vim?
Another example. https://github.com/ggandor/leap.nvim Leap provides great paragraphs giving overviews of what it does and why it is designed the way it is, including some compare and contrast with other plugins.
-
find-extender.nvim A Plugin that extends the nvim find command
Nice, but you've reinvented the wheel :) https://github.com/goldfeld/vim-seek -> https://github.com/justinmk/vim-sneak -> https://github.com/ggandor/leap.nvim
What are some alternatives?
When comparing pact.nvim and leap.nvim you can also consider the following projects:
nvim-lua
hop.nvim - Neovim motions on speed!
neorg - Modernity meets insane extensibility. The future of organizing your life in Neovim.
vim-easymotion - Vim motions on speed!
lightspeed.nvim - deprecated in favor of leap.nvim
mini.nvim - Library of 35+ independent Lua modules improving overall Neovim (version 0.7 and higher) experience with minimal effort
hotpot.nvim - :stew: Carl Weathers #1 Neovim Plugin.
hibiscus.nvim - :hibiscus: Flavored Fennel Macros for Neovim
avy - Jump to things in Emacs tree-style
vim-sneak - The missing motion for Vim :athletic_shoe:
quick-scope - Lightning fast left-right movement in Vim