kommentary
vim-fugitive
kommentary | vim-fugitive | |
---|---|---|
14 | 114 | |
533 | 19,314 | |
- | - | |
2.9 | 8.1 | |
5 months ago | 9 days ago | |
Lua | Vim Script | |
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.
kommentary
-
A pragmatic approach to migrating from VSCode to Neovim
Indent-blankline to draw indentation guides, nvim-autopairs to automatically complete pairs of brackets and quotes (I didn’t know I couldn’t live without it), nvim-ts-autotag to autocomplete pairs of tags as well, targets.vim to target what is inside or outside the mentioned pairs and vim-surround to manage all those pairs with few keystrokes. Kommentary to comment and uncomment lines of code, nvim-cursorline to help locate where the cursor is and nvim-colorizer because I am cheeky. Vim-abolish is definitely an interesting one. I decided to install it because of its case coercion capabilities, but it can do much more than that.
-
Question: Is it a requirement that plugins written in Lua require you to call the setup function?
Here’s an example of a lua plugin with no setup function
-
TakeTuesday: Comment.nvim tutorial
The one I use is kommentary.nvim. A) It works, and with embedded code too, but also b) the Lua underneath it is really good. It’s well-commented, tested, and just generally a good resource to learn Lua from (or at least it has been for me.)
-
Comment.nvim: new stuff that will make you Rick Roll.
A bit unrelated, but I wrote some tests for kommentary that might inspire you to create a test suite for this plugin too.
-
Comment.nvim: Simple and powerful comment plugin for neovim. Supports commentstring, dot repeat, left-right/up-down motions, hooks, and more
Dot repeat https://github.com/b3nj5m1n/kommentary/issues/41
-
Comment C/C++ line or block
I'm still using the tpopes plugin, so I don't really know about the Lua versions 😅. But I have heard good things about kommentary
-
nerdcommenter seems to better figure out what comment syntax to use than vim-commentary, but i like vim-commentary more at everything else
I've been using b3nj5m1n/kommentary . I's uses are similar to vim-comentary . It has option to use only single line comments . This can be used to avoid /* ... */ . You can try that out .
-
Aspiring plugin authors: look at kommentary
b3nj5m1n/kommentary is one that is relatively small, but big enough to be interesting. It is also *insanely* well documented and the overall code quality seems good to me.
-
commented.nvim, a commenting plugin that actually works with count.
I need a comment plugin that works in normal mode and virtual mode and accepts count. Neither does kommentary and nvim-comment provide counts, therefore I decided to write one for myself.
-
Custom keymap function does not work with `<Plug>` commands
I can import this function and use it with all my custom keybindings. However, it doesn't custom keybindings I want to use for the Kommentary plugin.
vim-fugitive
-
How to commit part of file in Git
the only reason I do some git stuff in vim and not _always_ in the shell, is because tpope is very thoughtful and fugitive.vim provides nice ways to deal with hunks or hunk partials (visually selecting a range within a hunk, for i.e.)
https://github.com/tpope/vim-fugitive/blob/master/doc/fugiti...
-
GitUI
I agree, navigating blame history is incredibly useful, if only to save you from asking the wrong person about a particular change.
Vim's Fugitive[1] can do this and also in Textmate to. So I would hope that most editor git plugins can.
1. https://github.com/tpope/vim-fugitive
-
What are some plugins that you can't live without?
Git: vim-fugitive and gitsigns.nvim
-
Is it too late to learn emacs as a vim lifer?
You'll want to invest the time in learning Magit, which will change your life once you get the hang of it (and I was a heavy user of Fugitive in Vim previously!), and it's unlikely you'll find a better integration with GDB anywhere else on the planet than with Emacs, though I can't say that empirically. You just need to take the plunge and start learning it, then cut over and take the hit in productivity one day when you're feeling adventurous. You'll ultimately become far more powerful than you've ever been. Especially if you delve into elisp over time. I use Spacemacs, which is bloated and has bugs, but it has so many features that I haven't undertaken the massive endeavor to replace it from scratch yet.
- Fugitive.vim: A Git wrapper so it should be illegal
-
webify.nvim - Open the current file in the remote's web interface (github or gitlab) or yank its URL
For an option that works on Vim, if you already use tpope's vim-fugitive, there's vim-rhubarb (for GitHub) and fugitive-gitlab.vim (for GitLab).
-
Vim users who work without any plugins, how does your vimrc look like?
I replace vim-fugitive with :! git
-
Switching from Emacs. My experience
The only thing I truly miss from Emacs is [Magit](https://magit.vc/) since I still consider it the best git wrapper available. It is just too good. Unfortunately [Neogit](https://github.com/TimUntersberger/neogit) is not quite there yet although I hope it makes it at some point. I didn't like [Fugitive]https://github.com/tpope/vim-fugitive), but I ended up finding a good enough workaround by using [Lazygit](https://github.com/jesseduffield/lazygit) through [Toggleterm](https://github.com/akinsho/toggleterm.nvim).
-
I like Tabasco.
I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.
-
[Neovim] Meilleure intégration GIT pour Neovim?
Edit: je viens de trouver [https://github.com/tpope/vim-fugitive de Val
What are some alternatives?
nvim-comment - A comment toggler for Neovim, written in Lua
neogit - An interactive and powerful Git interface for Neovim, inspired by Magit
vim-commentary - commentary.vim: comment stuff out
vim-gitgutter - A Vim plugin which shows git diff markers in the sign column and stages/previews/undoes hunks and partial hunks.
Comment.nvim - :brain: :muscle: // Smart and powerful comment plugin for neovim. Supports treesitter, dot repeat, left-right/up-down motions, hooks, and more
lazygit.nvim - Plugin for calling lazygit from within neovim.
nvim-ts-context-commentstring - Neovim treesitter plugin for setting the commentstring based on the cursor location in a file.
gitsigns.nvim - Git integration for buffers
commented.nvim - Neovim commenting plugin in Lua. Support operator, motions and more than 60 languages! :fire:
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
tcomment_vim - An extensible & universal comment vim-plugin that also handles embedded filetypes
lazygit - simple terminal UI for git commands