vim-plug

> To get Neovim kind of things to be anywhere near usable for modern day development work, you need to bolt a file browser, intellisense, command line section, remote editing section, container plugins, plugin installer, settings section etc etc on top of it Why? Neovim has multiple package managers. It has GUIs like https://github.com/neovide/neovide, it has support for LSP which can do something? Many people are comfortable with programming in an environment like that It also has a terminal (even though if you use neovim you probably prefer to open terminals outside the IDE) and support remote editing too Here are some links https://github.com/wbthomason/packer.nvim & https://github.com/junegunn/vim-plug https://neovide.dev/ https://neovim.io/doc/user/nvim_terminal_emulator.html https://neovim.io/doc/user/remote.html

Thx for the tip. I managed to get it working. Here are the additions to ~/.vimrc in case anyone is interested (this after installing vim-plug https://github.com/junegunn/vim-plug#unix and running :PlugInstall as per goyo instructions: set wrap linebreak nolist call plug#begin('~/.vim/plugged') Plug 'junegunn/goyo.vim' call plug#end() "Goyo settings let g:goyo_width = 60 let g:goyo_height = 999 let g:goyo_margin_top = 0 let g:goyo_margin_bottom = 0

You can have all that in vim - it just takes some set up. syntax highlighting: https://github.com/sheerun/vim-polyglot completion: https://github.com/neoclide/coc.nvim file browser: https://github.com/preservim/nerdtree how to install these plugins: https://github.com/junegunn/vim-plug

https://github.com/junegunn/vim-plug It's dead simple. No, it doesn't come out of the box, but it takes literally 5 minutes to install a plugin manager and you only have to do it once; afterwards, installing, updating or removing plugins takes literally seconds.

I'm relatively new to Vim (~4 months). I used the "learning by doing" approach by forcing myself to use Vim to write C and Python at work. I had two main reasons for learning Vim: (1) Vim is everywhere, so it must be worth it to learn the basics at least; and (2) modal editing felt easier on my wrists than the standard mouse + shortcuts approach I ended up using in other IDEs. Here is my advice: 1. Start with only a theme in your .vimrc, so no plugins or non-standard key bindings. 2. Use Vimtutor (or any other tutorial) to learn the basics: normal vs. insert mode, movement, manipulation, yank/paste (+ clipboard), splits, buffers, and searching. 3. As you write code, you will find yourself wanting to know how to do X. This is where Google and a simple "cheatsheet" file come in. Once you find out how to do X via Google, add an entry to your

The Emacs package list has a description field on the right, a shortcut for more info (?) and after it's installed you've got C-h m and often info pages (C-h i). What's wrong with that? Vim has no unified plugin structure, there are several plugin manager packages (often installed via git clone). I personally use vim-plug[i] which is more on the minimal side, but there are others like pathogen or vundle. No real centralized plugin repository like melpa, I don't think one of the plugin managers I've used had some kind of common install-screen. You mostly enter the github address and execute the package update vimscript. I've seen more Emacs info packages than :help docs, but in most cases I'm browsing the githup README.md/.org anyways. [1]: https://github.com/junegunn/vim-plug

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/vim-fugitive * vim-test. A plugin that helps you run tests from inside of Vim. https://github.com/janko-m/vim-test Outside of that, switch to NeoVim if you haven't already (https://neovim.io/). Or give Oni a chance, it looks really promising (https://www.onivim.io/).

I was operating under the impression that a single asterisk would muck up the Markdown parsing on HN. Turns out I'm half wrong it seems. Some work. With the italicised tests below, the first has a prepended asterisk, the second has an appended one. * Test Test* Test Test Test * I think I just started using daggers because U+2020 was super easy to remember and to avoid Markdown issues and the habit has stuck. You don't by any chance use Vim, do you? I use the Unicode plugin[0] by Christian Brabandt in Vim to quickly search for Unicode characters. You can use vim-plug[1][2] by Junegunn Choi, for instance, to install it and keep it updated or just install it manually yourself. call plug#begin('~/.vim/plugged') Plug 'https://github.com/chrisbra/unicode.vim' call plug#end() Then within vim type :UnicodeSearch dagger to search for d

Yeah: :PlugUpdate See https://github.com/junegunn/vim-plug EDIT: formatting

For an easy start, use a sane defaults plugin like sensible.vim [1] or vim-simple-defaults [2] (more opiniated). Also, use vim-plug [3] with few plugin like ctrlp, nerdtree, nerdcommenter and vim-simple-complete [4].) [1] https://github.com/tpope/vim-sensible [2] https://github.com/maxboisvert/vim-simple-defaults [3] https://github.com/junegunn/vim-plug [4] https://github.com/maxboisvert/vim-simple-complete I am the author of [2] and [4].

I am sorry for that issue, and sorry for all the emails,but SpaceVim is not only copy the name of spacemacs,it has many important ideas of spacemacs, such as layers(plugin and config groups), leader guide,and mappings fuzzy searching. why I create SpaceVim, instead of support space-vim, I think space-vim is just a copy of https://github.com/ctjhoa/spacevim and https://github.com/Tehnix/spaceneovim-layers and https://github.com/Tehnix/spaceneovim BTW space-vim's some syntax script is copy from https://github.com/junegunn/vim-plug and install script is just copy from spf13. so I do not want to support it, but when I create SpaceVim, and post blog anout SpaceVim, the author of space-vim comments a lot of unfriendly message. and here is the link. so I will apologies to all the people who receive my emails about SpaceVim, but I will not apolo

I now use https://github.com/junegunn/vim-plug - you can setup a one-liner in your Vimrc to download and set it up, then :PlugInstall and you're done (similar to what they have in the readme but I linked to a specific hash on GitHub instead of master). I also keep a separate file that lists the plugins to install and the source that from my main .vimrc. A lot of my coworkers have wanted my main vimrc for an "out of the box setup" of Vim and found it best for them to specify their own plugins rather than just blindly use mine - it also makes it easier for them to grab the latest copy without any conflicts.

I would recommend neovim. Configuring it should be as easy as symlinking your vimrc and .vim directory: https://neovim.io/doc/user/nvim.html#nvim-from-vim For packaging I suggest using vim-plug. It's super simple and super fast: https://github.com/junegunn/vim-plug

It's been linked in this thread already, but I would recommend changing to vim-plug since it has less clutter, see https://github.com/junegunn/vim-plug/wiki/faq#migrating-from... I've also run into coworkers having some weird transient issues that were fixed when I got them to change to vim-plug. I can't say for sure that's what fixed it of course, but it's now a bit of personal superstition.

I'm genuinely curious why you'd really want native package loading in vim, except for purity's sake. If you're already using third party packages, is it much worse to just add a package manager? I've been using junegunn's excellent `vim-plug`[0] for a while now and it's worked really well. Some of the benefits I can see over the native approach here: - Declarative configuration suitable for version control. - Parallel installation/update. - Run scripts or makefile on install/update. - On-demand loading based on open filetypes. [0]: https://github.com/junegunn/vim-plug