adapt flavour changes as done in vim-classic (rather than have a no_x11
flavour, the default is now no_x11; in this case, to cope with updates
from old versions, @pkgpath is built dynamically and passed via a var
to PLIST). reduce other differences to vim-classic makefile.
in upstream build infrastructure and this is now happy. let me know if
you run into problems with parallel builds with this.
(note: with some configs, the last update resulted in ^G not showing
the line number, this seems to be related to upstream change about ruler:
https://github.com/vim/vim/commit/ba36510920654a52d8b5908f5a61c6969bb31942
if affected, try 'set noruler').
Fixes path traversal problem in zip/tar plugins; archives with ../ paths
can result in possibly-unexpected file writes. The victim must edit such
a file using Vim which will reveal the filename and the file content.
package while there. the byte saving in the default install isn't worth
the extra hassle at update time (which is already tricky due to evim,
gvim and friends which are only in the gui installs).
pvk@ sent me a diff to fix some issues with missing dir creations due
to badly placed files, but I thought I'd go with this approach instead.
updates handled with @conflict @pkgpath as needed (relying on the old
packages which had @pkgpath ${BASE_PKGPATH} that means they match nicely
with the default new pkgpaths, avoiding the need for messy flavour
handling).
For the xxd tool, when outputting colored hexdumps using the -R command
line flag, together with -g1 (group every byte), -c 256 (format 256
octets per line), -d (show offsets in decimal) and -o <large_numer> (add
offset to the file position), the buffer used to write to may overflow.