I still keep vim around for huge files though. I work daily with NASTRAN input and output files, routinely multiple 100 mb, sometimes multiple-gb. I edited a 10gb file earlier this week and vim didn't choke up too much. Best editor I've found so far for huge files.

But sometimes there are merge conflicts. I've settled for xpra and kdiff3 as the mergetool. I just can't handle the problem without a GUI tool.

[1]: https://github.com/jgdavey/tslime.vim/

https://github.com/epeli/slimux

https://github.com/julienr/vim-cellmode

I have a nice 'generic-eval' operator in evil that lets me select via motions and eval the result. This is the best experience I've found so far. Documented here: https://gist.github.com/ad2b435bfdf2ec5f0b4d57aa8ea40df6

The superior solution you are looking for is the package called elpy.

It provides this, linting via flycheck, contextual auto-completion via company-mode, etc etc.

I wouldn't know how to survive without it. It's almost a full IDE in itself.

[0]: https://research.swtch.com/acme

Even though I write ruby and javascript all day, I still like to go and read how others are using vim. I usually walk away with a keybinding or plugin that makes my life better.

https://github.com/jalvesaq/Nvim-R

Not to mention you can share your command line shell session/screen with other people!!

Man. https://linux.die.net/man/1/tmux

Or if you're not into the whole brevity thing: https://linux.die.net/man/1/tmux

Try it with a friend the first time.

Using tmuxinator, I might set up a config for a rails project, for instance.

That way when I start tmux I get a vim editor in one window, a bash prompt in the next (for git), a rails server in the third, tests in the fourth, maybe another process in the 5th like sidekiq or something if required. Note, these (tmux-)windows all live inside of one terminal window.

So once you spend about 2 minutes writing that config, you can always start up your environment with tmuxinator start project-name and a few seconds later you're good to go.

Screen is a similar program.

That's why, while I use VIM when I have to, I much prefer the technology to handle automatically whatever it can. Like maintaining states, making them obvious and offload any fruitless decision making.

I use a macbook pro with iterm2, and I prefer to use a terminal multiplexer instead of tabs or the native screen split of iterm2.

If you ssh remote boxes a lot, it is very useful because you will not lose your session in case of an occasional disconnection.

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 apologies to the author of space-vim.

I'm talking the full shebang.

   * Autocomplete/Autoimporting (Static Analysis backed by compiler output)
   * Formatting
   * Linting
   * Fast or able to run over a slow SSH connection. 
   * Default error resolutions (if test() throws an exception generate a try { })
   * Global refactoring
   * The idea of a project (Creating, building, export/importing, libraries, dependencies)
   * Automatically generated & maintained building system at the click of a run button
   * Documentation at a single click or on hover if possible
   * Integrated console for running a project
   * File and source manager that should be easy to use
   * Binding profiles for Eclipse, NetBeans, JetBrains, VS20XX, ReSharper

   * Formal Method Verification? 
   * Coloring/styling of the entire TUI
   * Simple to interact with menus
   * Rust, Go, JavaScript (Browser & Node), Java, Scala, C, C++, PHP, Python support 
   * Pluggable language support that allows the plugin to provide static analysis & compiler data

    [TYPECHECK]
    ignored-modules = ssl,pyodbc

Add it to your `ftplugin/python.vim`. Requires you to have activated the Conda environment before opening the Python file, uses hard-coded Python versions, doesn't work with multiple environments, doesn't bother with `os.path.join` so no Windows compatibility, etc etc. Like I said: a hack.

  " Cheap trick to use the Conda environment with omnicompletion
  python3 << EOF
  import os
  import sys
  cenv = os.environ.get('CONDA_PREFIX')
  if cenv is not None:
      # Taken from `sys.path` as reported by ipython
      sys.path.insert(0, cenv + '/lib/python3.5/site-packages')
      sys.path.insert(0, cenv + '/lib/python3.5/lib-dynload')
      sys.path.insert(0, cenv + '/lib/python3.5/plat-linux')
      sys.path.insert(0, cenv + '/lib/python3.5')
      sys.path.insert(0, cenv + '/lib/python35.zip')
      sys.path.insert(0, cenv + '/bin')
  EOF
  set omnifunc=python3complete#Complete

Every so often when vim irritates me I try out PyCharm or vm-whatsit, and while IDE's do have better viz for some use cases, the actual act of manipulating code in-buffer never comes close to speaking vim. And I always add the vim plugin, without them the tool would be of no use to me whatsoever.

I hope someday some tool will eclipse (no) vim, but that's simply not the case in 2017.

More useful, IMHO, is the general solution of jumping to the definition that would be resolved by the python interpreter, regardless of location. For that, the key binding will depend on the plugin. For `jedi-vim`, you use `<leader>d` [0].

Incidentally, if you're new to using VIM as a python IDE, also note the value of `jedi-vim` providing Python docstrings via the standard VIM keybinding `K`. This is also mentioned in [0].

[0] https://github.com/davidhalter/jedi-vim#features