"The vim-surround plugin is so useful that it should probably be built into Vim." I couldn't agree with this more. Also undotree [1] should be built into Vim as well. Vim represents undo/redo under the hood as a tree, which is absolutely incredible once you have a plugin that unlocks it, but the built-in facilities for traversing that tree could be charitably described as "dismal". Vim's undo tree makes a solved prob…
Clickable link for [1] [1]: https://github.com/mbbill/undotree
Vim after 15 Years
161–170 of 176 posts
Re: Vim after 15 Years
#162I spent forever tweaking my plugins, now I just use SpaceVim and love it.
The default settings required very little changes for me and I've adjusted to their (clever) default key shortcut scheme.
Re: Vim after 15 Years
#163Earlier quoted context omitted.
Is that pronounced "space macs" or "spacky macs"?
"Space Emacs"
Sorry, that's not correct.
"Space Macs"
Re: Vim after 15 Years
#164Earlier quoted context omitted.
>in-line code documentation What do you mean by this? Like folded comments? >debugger So, gdb? >unit tests You can write unit tests in vim. You can also run them, obviously. >refactoring Again, what do you mean? Now it feels like you are just listing stuff or maybe I just don't know what refactoring actually means. >file browser/project support Granted the build in file explorer is pretty stupid, but the standard `:f…
For intellisense/documentation it means having method names, arguments, types, and short summaries pop up as you’re typing. E.g “print” might complete or printf and give you all you need to know to use it on the spot. While vim has autocomplete, I’ve never seen this documentation feature (even typed argument listings) and it’s extremely valuable to me. Tags require a lot of manual work, so I consider them in the “wor…
The documentation thing exists, I just find it distracting, so I don't use it.
Tags just require you to have something like exuberant-ctags installed, then you can just run `!ctags -R .` from vim and you are golden (only needs to be done as you create more classes/functions/methods/whatever)
Most shit are just GUIs or wrappers for gdb. There are plenty to choose from if you so choose.
If your unit tests take super long that might be a sign they are bad. Also if you can run a single unit test in some way, you can do it with vim. Unless your IDE does some JIT magic on the side that for some reason can not be replicated in terminal.
>it’s UX is awful next to IdE Ux.
I don't like tomato soup, so you are wrong!
>Personally don’t want to cart around a whole folder of plugins on top of vimrc, sounds like a pain.
I have grand total of 3 plugins, none of which are required for me to do work. It depends on whatever you want, I've seen many people use ton of useless plugins which either reimplement something already present or just try to do things "the old way I'm used to" instead of just learning to do the thing in "vim way"
Re: Vim after 15 Years
#165Still awesome.
Re: Vim after 15 Years
#166Earlier quoted context omitted.
For intellisense/documentation it means having method names, arguments, types, and short summaries pop up as you’re typing. E.g “print” might complete or printf and give you all you need to know to use it on the spot. While vim has autocomplete, I’ve never seen this documentation feature (even typed argument listings) and it’s extremely valuable to me. Tags require a lot of manual work, so I consider them in the “wor…
The documentation thing exists, I just find it distracting, so I don't use it. Tags just require you to have something like exuberant-ctags installed, then you can just run `!ctags -R .` from vim and you are golden (only needs to be done as you create more classes/functions/methods/whatever) Most shit are just GUIs or wrappers for gdb. There are plenty to choose from if you so choose. If your unit tests take super lo…
I suppose it’s possible to get a pretty good env with vim (you’re losing a lot without a mouse), but damn it’s a lot of work to get there...
Before you tell me how it’s totally not, all the things you listed require specific knowledge, configuration, and then custom non conflicting keyboard shortcuts (unless you like manipulating your tools 10x slower than ide users). For me it’s just not worth the work. Vim is best for me in its default state, and I can still take advantage of it being available everywhere that way. Ides make crazy configured vim portable by being the default state of the ide and downloadable to any pc (with limits) from the internet. It’s a much lower maintenance approach for me. I’m glad vim works for you, but I find it hard to believe it’s a very practical choice (unless you’re extremely attached to your custom setup).
Also vim seems less discoverable to me. If something’s not a keybind you already set up, you need to look up plug-in docs, or tab through all the hundreds of possible commands. In ide land you open your command Paulette and type a relevant word or plugin name and everything you could do along with keyboard shortcuts is displayed. Not to mention it’s displayed in a way that doesn’t disrupt what you were already looking at. That’s a nice advantage of a GUI.
When I picked up vim and committed to it it’s because I read online it was better and probably thought it made me more badass, but eventually after a few years I returned to IDEs, because they’re genuinely better suited (imo) for programming. Vim is a headache for a second rate ide, and continues to be headache to use as you go (ctags for every language? Official language plugins? ...)
I get you like vim, but using vim seems stubborn to me.
Re: Vim after 15 Years
#167Earlier quoted context omitted.
The documentation thing exists, I just find it distracting, so I don't use it. Tags just require you to have something like exuberant-ctags installed, then you can just run `!ctags -R .` from vim and you are golden (only needs to be done as you create more classes/functions/methods/whatever) Most shit are just GUIs or wrappers for gdb. There are plenty to choose from if you so choose. If your unit tests take super lo…
I suppose it’s possible to get a pretty good env with vim (you’re losing a lot without a mouse), but damn it’s a lot of work to get there... Before you tell me how it’s totally not, all the things you listed require specific knowledge, configuration, and then custom non conflicting keyboard shortcuts (unless you like manipulating your tools 10x slower than ide users). For me it’s just not worth the work. Vim is best…
>I suppose it’s possible to get a pretty good env with vim (you’re losing a lot without a mouse), but damn it’s a lot of work to get there...
>unless you like manipulating your tools 10x slower than ide users
Imo using mouse alone makes you at least twice as slow as using keyboard shortcuts. Not only do you need to physically move your hand and find your mouse, then you need to locate your pointer (which might not even be on the same screen) then you need to swing it in the approximately right region of screen and search for the button to click. Only to return your hand back to familiar keyboard. All the while you probably could have just pressed 2-3 buttons and be done with it.
>Also vim seems less discoverable to me. If something’s not a keybind you already set up, you need to look up plug-in docs, or tab through all the hundreds of possible commands.
The handy `:help ` has so far served me well, when searching how to do stuff in vim.
Otherwise it is obviously up to your taste. I truly believe that you are wrong, just as much as you believe that I am. From my point of view you probably didn't give vim a proper chance (most likely you fell into the few big potholes that many beginners find themselves, which I'll admit is fault of the default vim configuration)
As for >ctags for every language? Official language plugins?
Excuberant-ctags have so far worked with me on all but one language (Robot Framework), but people have long told me that exuberant-ctags is bad and I should use something else that is more advanced, I just haven't bothered since it handles C++ and Python well and that's all I currently care about. For language plugins, I guess only thing I have is specific syntax file for Robot Framework, but that's again only because it's still uncommon tool, so support for it is lacking.
Re: Vim after 15 Years
#168Re: Vim after 15 Years
#169Re: Vim after 15 Years
#170Earlier quoted context omitted.
I have not heard any good argument for a leader key better than . f, t, b for fzf (and t is not a stretch on my keyboard layout)
The only thing preventing me from using is the slight lag it introduce each time is used in insert mode. It is bearable with ',', but I cannot stand it with . If it is possible to remove completely this lag (not simply reduce it), then it would be awesome.
The problem is not the leader itself, but instead the bindings you're setting using leader: Use nmap instead of imap so that the mappings aren't even checked during insert mode.