Hot answers tagged

29

You seem to simply have an unpatched version of vim, otherwise the :version command or the --version parameter would list the patches on the second line. For example on my machine it says: VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Sep 10 2014 09:36:33) Included patches: 1-207, 209-355, 357-430 This is "patchlevel" 430, but it skips patches 208 & 356....


16

Vim started as a clone of vi and has almost all of the commands and features of the original vi, plus a lot of enhancements. (See :help design-compatible.) It can be compiled into one of basically five configurations: tiny, small, normal, big and huge. (See :help :version.) It can also be configured at run time to disable the extended features and use only ...


15

Testing the value of the win64 feature should tell you: :echo has("win64") If the output is 1, then your Vim installation is 64-bit. See: :help has() :help feature-list and search for 64.


11

Since you're on Ubuntu, use the file command: $ file -L "$(command -v vim)" /usr/bin/vim.gnome: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=acb723f1249782755116f93ed45a30e7115ff423, stripped As you can see, my vim is 64-bit. We need to use -L since /usr/bin/vim on ...


10

Since you're on Ubuntu, verify if Vim is installed by running dpkg -l | grep vim Check the available alternatives to Vi by running update-alternatives --list vi Set your favorite alternative to Vi by running update-alternatives --config vi


7

Try the undotree plugin: Someone asked me about the difference with Gundo, here is a list of differences, or advantages. Pure vimscript implementation and no 3rd-party libraries(like python) is needed, don't worry about performance, it's not such a big deal for vim to handle this. The only dependency is the 'diff' tool which always shipped ...


6

Yes, they were both caused by changes to the packaging and unrelated to Vim itself. The first epoch bump (since all packages without an explicit epoch have an implicit 0 epoch) was introduced when the versioning of the package changed from x.y.patch-debrev to x.y-patch+debrev (i.e., 6.1.263-2 to 6.1-266+1). The latter sorts earlier than the former, so the ...


6

I am sorry, but you won't get happy with your ancient Vim 6.4 and plugins. Most of the scripting functionality have been added with the Vim 7 version and beyond. The old 6 version did only have very limited set of available functions (e.g. glob() was certainly one of them, but did only support String and int as data types.). So have a look at the errors: ...


5

Add this to your .vimrc if has('python3') let g:gundo_prefer_python3 = 1 endif I was getting similar error. The above worked for me (I am using Manjaro Linux, and installed community/python-neovim (Python 3 client for neovim)). Found at https://bitbucket.org/sjl/gundo.vim/issues/42/about-python3-support


5

A "pure" Vim way, just because we can: :let is_64_bits = match(strpart(readfile(resolve('/proc/' . getpid() . '/exe'), 'b', 1)[0], 4, 1), '\%x02') != -1 So, how does it work? Split up in multiple commands: Get the path to the Vim binary: :let file = resolve('/proc/' . getpid() . '/exe') Read the first "line" of the current binary. Reading a "line" makes ...


5

Quick command to tell if it's vi or vim vi -h this will display the help info in my case : $ vi -h VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug 7 2016 16:03:11) [... skip other info ...] So here i'm with VIM.


4

It seems that chocolatey could be the solution to your problem. It is a package manager for Windows. (With the ambition of being "sort of apt-get for Windows") If you are ready to use it to install your softwares such as Vim it then provides a choco upgrade <pkg> command to update your package. Fortunately, Vim is a package included in the list and ...


3

As described in /usr/share/doc/vim/NEWS.Debian.gz, the Debian packages have switched to building against Python3 for Stretch. If you upgraded a system to Stretch and didn't see this message, then I highly recommend installing the apt-listchanges package, so you are informed of important changes like this in the future. If you notice, when you ran :python ...


3

If you want more features (and something more up to date than whats in the apt packages), you have to compile it yourself. You say you are on Debian, and all these should work on that platform. You will first want to clone the repo and remove any existing vim installations. git clone https://github.com/vim/vim.git sudo apt-get remove --purge vim* Next,...


2

You don't need to use original vi program, just add following alias to your bashrc. alias vi='vim -u NONE'


2

I suspect https://github.com/vim/vim/pull/6970 and related https://github.com/vim/vim/issues/4405 Basically, before the patch it was impossible to put vim into full "default colors mode" as there were no way to do it -- :hi link survived :hi clear. Also cleared highlight groups were impossible to set with :hi def groupname .... I guess that ...


1

As it turned out, I was running an older version of Vim. Updating using the following "three-liners" solved the problem. sudo add-apt-repository ppa:jonathonf/vim sudo apt update sudo apt install vim vim-gtk3


1

This is solved by removing mac_precompose_path from the Vim source code. A fork where this is fixed can be found here: https://github.com/OskarPersson/vim I tested this by creating a Homebrew formula of the repository above.


Only top voted, non community-wiki answers of a minimum length are eligible