this includes new colour schemes. they aim to be more consistent in
different environments (e.g. between text and gui versions), but
in some cases significantly change what people are familiar with.
a copy of the old colour schemes is installed under the "legacy"
directory to make it easier to revert if desired. you can either use
them directly in config, or (probably better if you share config
files between machines) copy the relevant files from
/usr/local/share/vim/vim82/colors/legacy to ~/.vim/colors
which take priority.
for more information, see
https://github.com/vim/colorschemeshttps://github.com/vim/vim/issues/10449#issuecomment-1140195027=
which have big changes in particular to background colours - various themes went
from "no" background colour (i.e. dark on a dark terminal) to setting a light
background.
diff-wrangling for the "backout SIGTSTP changes" diff (re
https://github.com/vim/vim/pull/9422) because other changes have been
made to the upstream code (it's still broken)
Add patches to a few ports to build with ruby 3.0, mostly -fdeclspec to
CFLAGS or CXXFLAGS.
Bump ports where the default version change causes a package change.
OK kmos@
that is somewhat nasty on OpenBSD (https://github.com/vim/vim/issues/7079,
reported by Oliver Taïbi).
- shuffle some lang entries to the correct PLIST while there
CVE-2019-12735 Arbitrary Code Execution via Modelines
https://github.com/numirias/security/blob/master/doc/2019-06-04_ace-vim-neovim.md
"Beyond patching, it's recommended to disable modelines in the vimrc
(set nomodeline), to use the securemodelines plugin, or to disable
modelineexpr (since patch 8.1.1366, Vim-only) to disallow expressions in
modelines."
Follow the upstream recommendations for packagers and switch to
multi-packages:
devel/gettext -> devel/gettext,-runtime
devel/gettext-tools -> devel/gettext,-tools
(new) devel/gettext,-textstyle
