rneovim.git/test/functional/provider, branch floattitle

docs: fix typos (#20394)

2022-09-30T07:53:52+00:00

Co-authored-by: Raphael 
Co-authored-by: smjonas 
Co-authored-by: zeertzjq

fix(tests): remove irrelevant usage of display-=msgsep

2022-08-17T21:44:49+00:00

These were just added to avoid churn when changing the default
of 'display'. To simplify message handling logic, we might want
to remove support for printing messages in default_grid later on.
This would allow things like printing error messages safely in the
middle of redraw, or a future graduation of the 'multigrid' feature.

feat(server): set $NVIM, unset $NVIM_LISTEN_ADDRESS #11009

2022-05-03T13:08:35+00:00

PROBLEM
------------------------------------------------------------------------
$NVIM_LISTEN_ADDRESS has conflicting purposes as both a parameter ("the
current process should listen on this address") and a descriptor ("the
current process is a child of this address").

This contradiction means the presence of NVIM_LISTEN_ADDRESS is
ambiguous, so child Nvim always tries to listen on its _parent's_
socket. This is the cause of lots of  "Failed to start server" spam in
our test/CI logs:

    WARN  2022-04-30… server_start:154: Failed to start server: address already in use: \\.\pipe\nvim-4480-0
    WARN  2022-04-30… server_start:154: Failed to start server: address already in use: \\.\pipe\nvim-2168-0

SOLUTION
------------------------------------------------------------------------

1. Set $NVIM to the parent v:servername, *only* in child processes.
   - Now the correct way to detect a "parent" Nvim is to check for $NVIM.
2. Do NOT set $NVIM_LISTEN_ADDRESS in child processes.
3. On startup if $NVIM_LISTEN_ADDRESS exists, unset it immediately after
   server init.
4. Open a channel to parent automatically, expose it as v:parent.

Fixes #3118
Fixes #6764
Fixes #9336
Ref https://github.com/neovim/neovim/pull/8247#issuecomment-380275696
Ref #8696

test(python3_spec): use a pattern to match SyntaxError message (#17705)

2022-03-13T14:05:56+00:00

vim-patch:8.1.0999: use register one too often and not properly tested

2022-03-09T05:32:50+00:00

Problem:    Use register one too often and not properly tested.
Solution:   Do not always use register one when specifying a register.
            (closes vim/vim#4085)  Add more tests.
https://github.com/vim/vim/commit/9d7fdd403a3a9ee0d008b6dcbcd2ecc9ec0f57b7

[RFC] fix: has('python') error (#17252)

2022-01-31T14:06:46+00:00

* fix: has('python') error

* fix: functional tests

feat(provider)!: remove support for python2 and python3.[3-5]

2022-01-29T18:49:37+00:00

These versions of python has reached End-of-life. getting rid
of python2 support removes a lot of logic to support two
incompatible python versions in the same version.

refactor(tests): use assert_alive() #15546

2021-09-01T16:42:53+00:00

fix(eval): cherry-pick emsg changes from v8.1.0736

2021-08-12T16:16:33+00:00

v8.1.0736 made some changes for making some emsgs more specific.
Includes the change for Test_lambda_fails() in test_lambda.vim.
Adjust relevant functionaltests to expect the new emsgs.

This patch has been fully ported in my Blob port PR, but it hasn't been
merged yet, so just use what we need from it for now.

Required for v8.1.1821.

Tests(clipboard): Add test for block paste

2021-07-01T09:01:01+00:00