Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vim plugins I use

prakashdanish.github.io

Post reply on HN
Print view View original

61–70 of 93 posts

Re: Vim plugins I use

#61

Post by gkya »

baby wrote: post #10

How is the plugin management in vim? I use emacs and it’s a pain to setup. You need to modify a config file (.emacs) in order to add plugin lists (melpa). You then browse the list through a shortcut (M-x list-packages) and you only see names, no description or ways to look for something specific. Once you installed your plugins there are no real way to access a manual or learn them. Often you will need to modify conf…

Your comment is totally wrong. Any package that's more than a quick hack has inline documentation in a ;;; Commentary: blog, docstrings for all public variables and functions, and customisation options for setting variables with an interactive interface w/ documentation and accepted values integrated. Bigger packages come with info files. All sorts of help is accessible by a multitude of entry points, most bound to convenient and consistent shortcuts. Package system requires remote repositories just like any other package system, and Melpa is a third party repository, so that's not surprising at all. The GNU Elpa archive is configured by default. And the list-packages interface has package descriptions, and can show package details by a single keystroke. Selecting and installing/removing multiple packages is possible.

If configurability is a burden on you just quit Emacs because that's its biggest point which makes it a very productive tool. And just like a sponge won't clean your tabletop by itself if you don't put soap on it and rub it to the tabletop, Emacs can't do anything for you if you don't learn how to use it and actually use it.

Re: Vim plugins I use

#62

Post by sandov »

I've doubted for long about learning Vim or Emacs.

I like the default vim keybindings, but I don't like having to install plugins in order to make my editor usable, I like the batteries-included concept.

But when I try to learn Emacs I can't accept the fact that I have to press M-v to go up one screenful. It must become really uncomfortable really fast.

Re: Vim plugins I use

#63

Post by AdamGibbins »

pfranz wrote: post #60
jessaustin wrote: post #22

Earlier quoted context omitted.

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.

I have a plugin manager that can help you with that! 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.

Git submodules handle that for me, also allows me to easily rollback.

Re: Vim plugins I use

#64

Post by MrBingley »

ddevault wrote: post #28

This list is far from conservative. Vim isn't an IDE and shouldn't be made into one - effective vim users ^z out of vim and use Unix as their IDE. Here's my more conservative plugin list: https://git.sr.ht/~sircmpwn/dotfiles/tree/.vimrc fugitive: I use this for the sole purpose of :Gblame because the command line blame tool that ships with git is frustrating to use. ctrlp is there for opening files quickly in large c…

> effective vim users ^z out of vim and use Unix as their IDE.

As someone who used to do this, I can tell you it's not very effective. For example, build systems. I work with a lot of C++ code, and after making changes I used to ctrl-z to the terminal and then `make` manually ... only to get blindsided by lines and lines of error messages, many due to a lot of trivial syntax errors. Using YouCompleteMe may not be very minimal or "Unixy", but having error messages inline with my code and being able to correct them as I work is invaluable. Maybe your experience is different, but I couldn't get it to work for me. ¯\_(ツ)_/¯

Re: Vim plugins I use

#65

Post by mattbreeden »

sandov wrote: post #62

I've doubted for long about learning Vim or Emacs. I like the default vim keybindings, but I don't like having to install plugins in order to make my editor usable, I like the batteries-included concept. But when I try to learn Emacs I can't accept the fact that I have to press M-v to go up one screenful. It must become really uncomfortable really fast.

You can try Evil mode which gives you vim keybinds in Emacs: https://github.com/emacs-evil/evil

Re: Vim plugins I use

#66

Post by [deleted] »

pfranz wrote: post #60
jessaustin wrote: post #22

Earlier quoted context omitted.

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.

I have a plugin manager that can help you with that! 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.

[deleted]

Re: Vim plugins I use

#67

Post by skosch »

sooheon wrote: post #59
suprfnk wrote: post #48

Earlier quoted context omitted.

Do you know how doom-emacs compares to spacemacs?

More opinionated, a little more bare-metal, a lot worse bus factor.

All of those things are true!

Overall, it's a solid alternative to Spacemacs that not enough people know about.

Spacemacs markets itself much better and I tried it first, but found it to be bloated to be point that it noticeably impacted performance. E.g. start-up time was 10+ seconds; ~2s with doom (and doom doesn't feel any less feature-complete).

As for the bus factor, doom has the maturity of a 4-year-old project; it won't just fall apart on you. It is mostly a one-man show, but Henrik is still very active and super quick to respond to issues.

Re: Vim plugins I use

#68

Post by sodapopcan »

crehn wrote: post #44

I 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

I've never really understood this argument. Using vim locally with a bunch of plugins and then vanilla vim remotely is really the exact same thing as using any other editor locally and vanilla vim remotely.... especially if you are using vim bindings in said other editor!

In any event, I just mitigate this problem by not overriding a bunch of standard behaviour. Also, none of the many plugins I use modify any standard behaviour in any serious way, they just help speed up certain actions when working in a large code base. There is very minimal context switch for me when editing a file remotely.

Re: Vim plugins I use

#69

Post by sodapopcan »

snarfy wrote: post #21

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…

If you want a "file drawer" that is always open, nerdtree ain't great, but furthermore, the whole "file drawer" concept doesn't really work in vim. I personally prefer nerdtree to the builtin netrw but the "killer setting" for me is "close nerdtree after opening a file". nerdtree is super useful as a tree explorer but you'll have a much better time if you don't treat it as a "drawer".

Re: Vim plugins I use

#70

Post by mattbreeden »

aquova wrote: post #36

People seem to swear by NerdTree, but I personally don't see the purpose of it. Sure it may be nice to see your file structure sometimes, but having a terminal open or even just the actual folder window open solves that. Everything else can be done with the built-in :Ex command, which lets you navigate to open files, create new files, rename, delete, mostly everything you want. As for other plug-ins, there are a few…

> Sure it may be nice to see your file structure sometimes

And you can just use the built in :Ex for that

Post reply on HN