I gave up trying to make Vim into an IDE. It's a text editor. It's an excellent one, but that's what it does. The plugins just aren't very good. NerdTree is not a good file browser. None of the autocomplete/intellisense works very well. It does work, but requires a lot of setup, and let's be honest, a TUI isn't the best way to interact with autocomplete dropdowns. Most of the IDEs have vim like features or plugins. I…
Text editors and IDEs are quite different. For everz we've ben trying to shove one into the other. Every IDE has a sort of shitty text editor. Every text editor tries to make a shitty IDE. Can someone please ackgnowledge that the reality is that neither is a good approach? I wish that I could have complete integration between VIM and JetBrains suite. Would be nice if the JetBrains platform could render a VIM inside i…
Vim plugins I use
51–60 of 93 posts
Re: Vim plugins I use
#52I gave up trying to make Vim into an IDE. It's a text editor. It's an excellent one, but that's what it does. The plugins just aren't very good. NerdTree is not a good file browser. None of the autocomplete/intellisense works very well. It does work, but requires a lot of setup, and let's be honest, a TUI isn't the best way to interact with autocomplete dropdowns. Most of the IDEs have vim like features or plugins. I…
Re: Vim plugins I use
#53As an Emacs user, I'm so curious about vim packages. Does vim have packages that are akin to adding a major mode in Emacs? Some of the packages on this list look like the vim version of minor modes or little helper functions.
Vim has a limited number of "modes" -- insert, normal, command and visual. These are not analogous to Emacs modes AFAICT. A vim package/plugin typically modifies/enhances behaviour in these modes. Where they can, useful operations are bound to a key combination. You spend most of your time in Vim (when editing) in normal mode, executing deft movements and register usage to behave as a surgeon upon the text, as it wer…
Re: Vim plugins I use
#54Earlier quoted context omitted.
I don't see why being effective in vim means you ^z out of vim to run `ack` or `grep`, instead of pressing ^f (for example) to run Ack.vim on the and have the results displayed next to your code in a window that, when you select the item you want, opens that corresponding file in a buffer with your cursor already on the line in question. Certainly you don't need ack.vim, you could just ^z and do it the old fashioned…
Strictly speaking, one doesn't even need a plugin to use ack, ag or ripgrep from Vim. It is enough to set the "grepprg" option (perhaps also "grepformat") and then one can invoke the built-in ":grep" command. For example, to use ripgrep: set grepprg=rg\ --vimgrep\ --no-heading
Re: Vim plugins I use
#55Earlier quoted context omitted.
I don't see why being effective in vim means you ^z out of vim to run `ack` or `grep`, instead of pressing ^f (for example) to run Ack.vim on the and have the results displayed next to your code in a window that, when you select the item you want, opens that corresponding file in a buffer with your cursor already on the line in question. Certainly you don't need ack.vim, you could just ^z and do it the old fashioned…
>Certainly you don't need ack.vim, you could just ^z and do it the old fashioned way, but where is the utility in that? Because ack.vim can't be piped into other tools. You can't, for example, limit your search to the last 50 files modified. Or only to executable files. You can't pipe the results into sed or make matching files world-readable. Sure, you could install ack.vim, slow down vim's startup and bloat your in…
I rarely (if ever) need to make matches world readable from the context of text editing. When I do, there's nothing stopping me from using ^z, but until that day comes, a plug-in is going to be fewer keystrokes, faster, and better integrated with what I was already doing.
Re: Vim plugins I use
#56I personally use no plugins [1]. Zero friction moving from host to host. Vim is a great text editor, not a great IDE. For anything more sophisticated I prefer just switching to something like VS Code (with Vim bindings of course). [1] https://github.com/hoffa/dotfiles/blob/master/.vimrc
Tbh, the only thing that gets in my way are the exact tab-related settings you also have.
Re: Vim plugins I use
#57I gave up trying to make Vim into an IDE. It's a text editor. It's an excellent one, but that's what it does. The plugins just aren't very good. NerdTree is not a good file browser. None of the autocomplete/intellisense works very well. It does work, but requires a lot of setup, and let's be honest, a TUI isn't the best way to interact with autocomplete dropdowns. Most of the IDEs have vim like features or plugins. I…
Text editors and IDEs are quite different. For everz we've ben trying to shove one into the other. Every IDE has a sort of shitty text editor. Every text editor tries to make a shitty IDE. Can someone please ackgnowledge that the reality is that neither is a good approach? I wish that I could have complete integration between VIM and JetBrains suite. Would be nice if the JetBrains platform could render a VIM inside i…
Re: Vim plugins I use
#58I gave up trying to make Vim into an IDE. It's a text editor. It's an excellent one, but that's what it does. The plugins just aren't very good. NerdTree is not a good file browser. None of the autocomplete/intellisense works very well. It does work, but requires a lot of setup, and let's be honest, a TUI isn't the best way to interact with autocomplete dropdowns. Most of the IDEs have vim like features or plugins. I…
I've tried using vim plugins with different editors before, but they're always missing a few of the shortcuts that are in my muscle memory and drive me crazy. Also, being able to ssh into any machine and remotely edit code is pretty awesome.
The most productive vim keybinding I ever came across was:
noremap @q
Since the key to start a macro is q, you can quickly tap qq to record a macro to the q register (end it by pressing q again.) Then by whacking the space bar you can execute the q macro as many times as you'd like. Once you get into the rhythm of using it often even for small tasks, it can become a great optimization. Sometimes I use it with five or more different macros in a single minute. If you ever look forward in time and see that you're about to perform the same edit two or three times, pressing the q key three times total and the space bar once per execution (or only once with a count) will often be fewer keystrokes than had you performed the edit manually each time. Not to mention triumphantly smacking the space bar to repeat an edit is a great feeling.(Simple edits can be repeated using . which is another indispensable vim feature that sometimes gets missed by vi-plugins in other editors.)
Re: Vim plugins I use
#59Earlier quoted context omitted.
Those were my favourite neovim plugins as well. Oni is still a bit rough around the edges, and rendering is a little bit slow at times, at least on my machine. I now use doom-emacs [1] and haven't looked back. [1] https://github.com/hlissner/doom-emacs
Do you know how doom-emacs compares to spacemacs?
Re: Vim plugins I use
#60Earlier quoted context omitted.
- You can update all the plugins with PlugUpdate; furthermore, they are updated in parallel. - You can lazy load plugins - You can execute commands after a plugin update (e.g. building the new binary for youcompleteme) Those are the major points I think.
Lots of people like plugin managers. I prefer to use "git clone" and "stow". Much less magical, and I feel I have a better understanding of what's going on with my configuration.
Seriously, isn't part of the problem that vim by default looks for all plugins in one directory? Tim Pope's Pathogen does the minimum here and lets each plugin have its own directory (which translates to git repo). You're responsible for going to each directory and updating them.