5 ms·
I've made the, apparent, mistake of having some python plugins in my vim setup. The packaging of vim7 for Ubuntu 16.04, the vim8 PPA both end up leaving me wit
by linsomniac 10y ago
I've made the, apparent, mistake of having some python plugins in my vim setup. The packaging of vim7 for Ubuntu 16.04, the vim8 PPA both end up leaving me with all sorts of errors when I save files, particularly Python files. I had been using gvim in the terminal because of how it handles mouse events, but now I have only one choice for the vim that has Python in it it seems...
I had tried neovim in the past and just couldn't get it configured, so I went back to vim. That was maybe 6 months ago though.
So I nuked all my plugins and that's making it better but I'm missing my python lint and DNS serial number update helper, etc...
A few days ago I tried figuring out vim8's plugin stuff, and either the searches I'm doing are not right, or there is very little documentation/discussion on it, because I just didn't get anywhere.
So now I'm trying to figure out where I go from here... Possible choices:
- Neovim, since I have to "start over" with vim anyway.
- Figure out the vim8 plugins, spending more time with it.
- Atom? It looks sweet from my playing with it, but I'd probably only use it for serious coding, which I don't do that much, I'm a sysadmin and always in and out of editors in the terminal.
- Something else (Wingware, Pycharm, ?)
Looks like I need to add something to my schedule to figure this mess out. I'm leaning towards figuring out neovim, because it has a great velocity.
- usernamefornow 10y agoIf you just need a vim with python, it's fairly simple to compile from source. You can start by modifying what's given here: https://github.com/Valloric/YouCompleteMe/wiki/Building-Vim-from-source https://github.com/Valloric/YouCompleteMe/wiki/Building-Vim-... About the package system, yes there really isn't any documentation at all because it doesn't do all that much in the first place. I would suggest just using vim-plug or another package manager. Also, there really isn't anything to learn in Neovim. Mainly just try out the terminal emulator and come up with some terminal maps.
- linsomniac 10y agoSorry, I'm an operations guy, so compiling from source is never simple. :-/ (I know most people don't understand this, but in my world "./configure; make" just leads to a world of pain) vim-plug sounds like something I should investigate. I hadn't heard of it before now, I had been using pathogen for the last year or two. I've been playing a bit with neovim and have it working happily now. Not sure what the problem I was having last time I tried, but it was just a nightmare (granted, I had only given myself 15m to try it).
- JelteF 10y agoI 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 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 https://github.com/junegunn/vim-plug
- tcfunk 10y agoI've been using Spacemacs(http://spacemacs.org/ http://spacemacs.org/) for some time now, and like it quite a bit.
- linsomniac 10y agoI haven't looked at spacemacs before. Looks interesting as an option in the various vi variants.
- justinmk 10y agoThe `:CheckHealth` command added in Neovim 0.1.5 should help with python/ruby/general sanity checks. It has more improvements in 0.1.6 which will be released soon.
- linsomniac 10y ago:checkHealth is awesome!
- karl42 10y agoDid you try installing a vim with python support (e.g. vim-nox-py2)?