rneovim.git/test/functional/provider/python3_spec.lua, branch v0.3.6

provider: improve error message if provider is missing (#9487)

2019-01-13T00:49:07+00:00

Move `has_eval_provider()` check to `eval_call_provider()` to make sure that
every code path calls it first.

Previously we would, when pynvim was missing, get a nice error message for
`:python3 1`, but not for `:py3file blah`.

Fixes https://github.com/neovim/neovim/issues/9485

provider: repurpose E319

2018-12-12T00:26:21+00:00

In Vim (and some vestigial parts of Nvim) E319 was a placeholder for
ex_ni commands, i.e. commands that are only available in certain builds
of Vim.  That is obviously counter to Nvim's goals: all Nvim commands
are available on all platforms and build types (the remaining ex_ni
commands are actually just missing providers).

We need an error id for "missing provider", so it makes sense to use
E319 for that purpose.

ref #9344
ref #3577

provider/RPC: apply_autocmds_group(): fix double-free

2018-03-24T10:01:24+00:00

During provider dispatch, eval_call_provider() saves global
state--including pointers, such as `autocmd_fname`--into
`provider_caller_scope` which is later restored by f_rpcrequest().

But `autocmd_fname` is special-cased in eval_vars(), for performance
(see Vim patch 7.2.021; this is also the singular purpose of the
`autocmd_fname_full` global. Yay!)

If eval_vars() frees `autocmd_fname` then its provider-RPC-scoped alias
becomes a problem.

Solution: Don't free autocmd_fname in eval_vars(), just copy into it.

closes #5245
closes #5617

Reference
------------------------------------------------------------------------

Vim patch 7.2.021
https://github.com/vim/vim/commit/f6dad43c98f47da1ff9d8c99b320fc3674f83c63
Problem:    When executing autocommands getting the full file name may be
            slow. (David Kotchan)
Solution:   Postpone calling FullName_save() until autocmd_fname is used.

vim_dev discussion (2008): "Problem with CursorMoved AutoCommand when
Editing Files on a Remote WIndows Share"
https://groups.google.com/d/msg/vim_dev/kj95weZa_eE/GTgj4aq5sIgJ

test/python: less-noisy Python skip-message

2018-02-12T12:24:48+00:00

Developer can use :checkhealth to get more details, don't need to blast
the details in the skip-message every time.

functests: Replace check_provider -> missing_provider with err report

2017-05-13T00:06:50+00:00

functests: Test invalid behaviour

2017-05-13T00:06:30+00:00

Test correctly fail for oneline ruby, python and python3.

api: Do not truncate errors <1 MB. #6237

2017-04-23T21:44:29+00:00

Closes #5984

functests: Check logs in lua code

2016-06-10T18:50:49+00:00

It is otherwise impossible to determine which test failed sanitizer/valgrind
check. test/functional/helpers.lua module return was changed so that tests which
do not provide after_each function to get new check will automatically fail.

Ensure a session is running before attempting to do Python detection.

2015-11-04T10:01:22+00:00

test: Check for installed Python module with Vimscript function.

2015-09-26T22:03:06+00:00

Use the existing Vimscript function provider#pythonx#Detect()
to determine whether the Neovim Python module is installed and
Python 2/3 tests can be run.