ZyX-I

Here I will list all incompatibilities between old and new VimL implementations. Some may be fixed, so it is also a place for discussion. Please discuss incompatibilities with separate issues in separate issues.

Expressions parser incompatibilities

• Dot subscripts are not always read correctly (#240).
• E15 errors are not not just “E15: Invalid expression”: there are (invalid expressions)
• “E15: expected variable name” (\x80\xFD\x52)

ZyX-I

+ set -u
+ PROJECT_ROOT=/doc
+ cd /doc
+ test -x /doc/docker/build.sh
+ /doc/docker/build.sh
+ set -u
+ ARGS_make_pdflatex=LATEX=pdflatex
+ ARGS_make_xelatex=
+ ARGS_cmake_pdflatex=-DPREFER_XELATEX=false
+ ARGS_cmake_xelatex=

ZyX-I

www.viva64.com/en/w:1:1: error: Help: The documentation for all analyzer warnings is available here: http://www.viva64.com/en/w/.
./src/nvim/api/ui.c:57:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);
./src/nvim/api/ui.c:62:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);
./src/nvim/api/ui.c:128:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);
./src/nvim/api/ui.c:140:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);
./src/nvim/api/ui.c:145:1: warni

ZyX-I

# -*- coding: utf-8 -*-
"""
Go to Google Bookmarks: https://www.google.com/bookmarks/

On the bottom left, click "Export bookmarks": https://www.google.com/bookmarks/bookmarks.html?hl=en

After downloading the html file, run this script on it to generate a KML.

"""

ZyX-I

New python objects

vim.mappings/{buffer}.mappings:

Mapping-like object mapping mode constants to vim.modemappings objects below. Unlike vim.buffers iteration is being done for keys. Mode constants are described below in vim.current.mode object description, but for convenience additional constants are defined:

ZyX-I

#!/bin/sh
FILENAME="$1" \
vim -u NONE -N -S readfile-test.vim --cmd 'let AddFileName=$FILENAME'