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

81–90 of 93 posts

Re: Vim plugins I use

#81

Post by jessaustin »

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.

I'm doing that too. I clone into "~/.config/nvim/stow/", then stow figures out how to put all that stuff into the proper places. Occasionally there is a conflict, but that is usually for files that I don't want anyway, like "build" or "LICENSE".

Re: Vim plugins I use

#82

Post by icc97 »

I spent a day or two recently figuring out how to get the vim-airline (aka powerline) icons to work properly, going through pretty much every single font/theme option on Windows (even in the DOS prompt) and Linux. I added a dummies guide [0] to the Wiki.

For a Windows console user - it's worth noting that since they got 24-bit colours working in the console the work is now on-going to get the colours properly working in terminal Vim [1].

[0]: https://github.com/vim-airline/vim-airline/wiki/Dummies-Guid...

[1]: https://github.com/vim/vim/pull/2060

Re: Vim plugins I use

#83

Post by prakashdanish »

jamslater wrote: post #77

I think that https://github.com/simeji/winresizer is a good tool. we'll able to become windows resize easier.

I came across this before but since I was using tmux splits back then, this sounded like unnecessary overhead but now that I've been using vim splits excessively, this is proving to be a nice little addition.

Re: Vim plugins I use

#85

Post by pasabagi »

Sir_Cmpwn wrote: post #41
JackCh wrote: post #39

Earlier 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…

One thing I don't understand, is how do you handle mistakes with the 'unix-as-ide' approach? I was using sed to refactor. Now, I typically use bufdo %s/foo/bar/gc, because it's much more forgiving. It's the same story with a lot of stuff you can ctrl-z for - if you can do it inside vim, it's usually far easier to control and roll back.

Re: Vim plugins I use

#86

Post by burntsushi »

danidiaz wrote: post #45
JackCh wrote: post #39

Earlier 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

Small note: --vimgrep implies --no-heading, so you can drop --no-heading. :-)

Re: Vim plugins I use

#87

Post by tomcooks »

mhd wrote: post #19

Let's get this out of the way: "How to Do 90% of What Plugins Do (With Just Vim)": https://www.youtube.com/watch?v=XA2WjJbmmoM And if you want to see some crazy vim usage, there's always Damian Conway: https://www.youtube.com/watch?v=aHm36-na4-4

I keep a semi-pristine vimrc because of the first video, after having seen how heavy vim plugins can be on my low end equipment

Re: Vim plugins I use

#89

Post by C0d3r »

pasabagi wrote: post #85
Sir_Cmpwn wrote: post #41

Earlier quoted context omitted.

>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…

One thing I don't understand, is how do you handle mistakes with the 'unix-as-ide' approach? I was using sed to refactor. Now, I typically use bufdo %s/foo/bar/gc, because it's much more forgiving. It's the same story with a lot of stuff you can ctrl-z for - if you can do it inside vim, it's usually far easier to control and roll back.

Git helps you with those mistakes, otherwise, yes, very unforgiving

Re: Vim plugins I use

#90

Post by sebosp »

jherdman wrote: post #2

Here are some I find invaluable: * FZF. Perhaps the best fuzzy finder for Vim https://github.com/junegunn/fzf/ * ALE. Asynchronous Linting Engine, totally awesome. https://github.com/w0rp/ale * Polyglot. A "best of" language pack. https://github.com/sheerun/vim-polyglot * Plug. IMHO the best plugin manager going https://github.com/junegunn/vim-plug . * Fugitive. The best git wrapper there is https://github.com/tpope/…

What is the downside of using vim packs in contrast to vim plugins ? I just do cd ~/.vim/pack/start and from there I git clone the repos and that's it... In my case I usually work in a container and have different packs depending if I'm doing stuff with programming in rust or go or just do configuration management. I really loved the asynchronous functionality in vim8, any nice plugins that take advantage of it? For now I only use it to trigger cargo test and let finish at some point later on: https://github.com/sebosp/linuxtweaks/blob/develop/vimrc#L14...
Post reply on HN