Ok. Apparently on native vim in Arch there is no support for X so the +clipboard feature is missing.
To fix this, install gvim, which although conflicts with vim, which was my initial problem with it, retains the exact same functionality if you use
You still need to set clipboard=unnamed.
First off, Vim can only display a file in a single font, you can't use multiple fonts at the same time.
For gVim, you can use guifont to set this to Font Awesome:
set guifont=Font\ Awesome\ 14
Which seems to work fine.
For Terminal Vim, you will need to configure your terminal emulator to use Font Awesome.
For xterm, this doesn't seem to work, for gnome-...
n indent on
means "open the file called indent that is at the root of the working directory". Basically, you tell Vim to do something silly and… it does just that.
It should be:
filetype plugin indent on
Be more careful about what you copy and paste.
Thanks to x33a on the Arch forums, I was able to solve my problem. (https://bbs.archlinux.org/viewtopic.php?pid=1596987#p1596987)
I changed the python 3 flag from
This resulted in only python 3 being available.
I unknowingly had installed on my system the set of packages "vim-plugins".
Among these was "vim-jedi" which seems to be the one causing behavior I didn't want.
I used the package manager to remove it.
Thanks very much for the commenters who helped me diagnose this!
The problem was not in Vim's default Python interpreter.
The real root of the problem is that the last version of jedi-vim (0.7.0) was released in 2013 and did not work well with Python 3.
Since then Python 3 support in jedi-vim has been improved a lot.
We (Arch users) asked jedi-vim to make a new release. 0.8.0 has been released and now it is in the Arch ...
If the background is changing, then the colorscheme is changing it. You can either choose a colorscheme that doesn't do that, or try overriding the colorscheme.
autocmd ColorScheme * highlight Normal ctermbg=NONE guibg=NONE
The colorscheme may be designed around a particular background color, though, and there may be other highlight groups which need ...
I feel like an idiot. The test file doesn't have any non-ASCII characters in it, so there is nothing for file to look for that would tell it the encoding Vim is using. So I repeated the test with ä in it and it returns "utf-8" as desired.
In short, file was doing its best, and Vim was doing what I wanted it to do.
I worked around this problem by using the compile switch:
However, obviously it is just a workaround and the test failure will be a problem for anyone that wants to use netbeans with compiled vim.
One thing I've just seen is that if cpo contains <, then special characters like <leader> won't be handled right:
< Disable the recognition of special key codes in |<>|
form in mappings, abbreviations, and the "to" part of
menu commands. For example, the command
Well, so after some investigation I finally located a vundle file. It start from a lower-cased letter and that's why I did not find it at the first place.
It's located in /usr/share/vim/vimfiles/autoload/vundle.vim folder. To make vundle work with such a setup, the following tweaks to a config from vundle repo are necessary: