Opposed to Vim, 'F' is set by default in Nvim. But in combination with the API,
the "swap file exists" dialog wouldn't appear for some reason.
References https://github.com/mhinz/neovim-remote/issues/92
A buffer managed by nvr sets the b:nvr variable. It contains the channel IDs of
all connected nvr clients.
nvr clients understand two RPC messages, BufDelete and Exit.
The latter always required the exit code as argument and the former optionally
takes one as well now.
let exitcode = 1
for chan in b:nvr
call rpcnotify(chan, 'BufDelete', exitcode)
endfor
Closes#89
This release adds support for Python 3.7.
Previously we didn't allow that version because python-client had problems with
it, since arguments were named after keywords newly introduced in 3.7.
Fixed since of https://github.com/neovim/python-client/pull/274
Previously, when doing `nvr --remote-tab file` without an already running nvim
process, nvr would first start a new nvim process without any arguments and then
`:tabedit file`.
This would leave an empty first buffer and is not how Vim's `vim --servername
foo --remote-tab` behaves.
Now, nvr reuses the first buffer when starting a new process for any of the
--remote options.
`nvr -p` and friends are already working correctly.
Fixes#84
Previously we converted any path given to nvr to an absolute one. But then `nvr
http://example.com/file` wouldn't trigger netrw's BufReadCmd event and thus
download the file, because it would see an absolute path like
`~/http://example.com/file` and the netrw autocmd only matches on `http://*`.
Fixes#86
When you tag a commit on master and push it to GitHub, TravisCI will actually
run two builds, one for master and one for a branch named after the tag.
We use a conditional deploy stage. It will be only used if the git tag happens
to match a certain regexp.
By default the deployment provider only deploys for the master branch. That will
never be the case for our conditional stage. So we deploy for all branches now,
knowing it will only happen for tag branches anyway.