Hi, the installed system wide gvimrc runs "set nocompatible" and thus breaks a lot of previous settings in custom $HOME/.vimrc. As you can read in the user manual about compatible: CAREFUL: Setting or resetting this option can have a lot of unexpected effects: Mappings are interpreted in another way, undo behaves differently, etc. If you set this option in your vimrc file, you should probably put it at the very start. It could be fine run "set nocompatible" in vimrc system-wide, but not in gvimrc. Regards
Auto-assigned to maintainer sunpoet@FreeBSD.org
Reassigning to myself. Submitter: is this still a problem?
Hi Adam, thanks you for rescue this bug. The issue is still open. See the following thread: https://groups.google.com/forum/#!topic/vim_use/66crU745cFc My workaround is comment the "set nocompatible" line in system wide gvimrc, and remember to do it in each vim upgrade. Regards
A commit references this bug: Author: adamw Date: Sat Oct 1 16:18:56 UTC 2016 New revision: 423078 URL: https://svnweb.freebsd.org/changeset/ports/423078 Log: - Don't set nocompatible in the gvimrc [1], bump PORTREVISION See also https://groups.google.com/forum/#!topic/vim_use/66crU745cFc - Mark as MAKE_JOBS_UNSAFE (thanks to Mat for the log): make[2]: "/wrkdirs/usr/ports/editors/vim/work/vim-8.0.0019/src/po/Makefile" line 4: Could not find ../auto/config.mk make[2]: Fatal errors encountered -- cannot continue PR: 197214 [1] Submitted by: jjuanino gmail Changes: head/editors/vim/Makefile
Committed a quick fix that just yanks that line out of the gvimrc. Thanks!