Hot answers tagged vim
You are confusing $(…) with <(…). You used the former, which passes the output as arguments to vimdiff. For example, if the last line of /path/to/foo contains bar bar bar, then the following command echo $(tail -1 /path/to/foo) is equivalent to echo bar bar bar Instead, you need to use <(…). This is called process substitution, and passes the ...
filereadable() or isdirectory() would be better choices than findfile() -- the latter one searches in a set of directories. BTW, findfile() returns nothing (an empty string) on my system for ~/.vim However, isdirectory() cannot process ~/, but fnamemodify() comes to the rescue. if isdirectory(fnamemodify('~/.vim/autoload', ':p')) execute ...
I think your file-type setting have gone some how wrong. At least in my VIM, python is in minor letter. what happen when you set the file type manually? :setf python
That built-in terminal is just a very bare one; it doesn't offer capabilities like color highlighting. If you want that, you need to either use terminal Vim, or launch the external command in a separate terminal window: :!gnome-terminal -x sh -c 'git diff file.c'
If you create your own syntax group names, like basicLanguageKeywords, then you'll have to create highlight settings for them. Stick to commonly used names so that your syntax settings work with most colour schemes. Checkout :h group-name: To be able to allow each user to pick his favorite set of colors, there must be preferred names for highlight groups ...
What is this ^M? The ^M is a carriage-return character. If you see this, you're probably looking at a file that originated in the DOS/Windows world, where an end-of-line is marked by a carriage return/newline pair, whereas in the Unix world, end-of-line is marked by a single newline. How could it have got there? When there is change in file format. How do ...
Only top voted, non community-wiki answers of a minimum length are eligible