rneovim.git/test/functional/insert, branch newfeatures

test: reorg #15698

2021-09-17T16:16:40+00:00

Problem:
Subdirectories like "visual", "insert", "normal" encourage people to
separate *related* tests for no good reason.  Typically the _mode_ is
not the relevant topic of a test (and when it is, _then_ create
an appropriate describe() or it()).

Solution:
- Delete the various `test/functional//` subdirectories, move
  their tests to more meaningful topics.
- Rename `…/normal/` to `…/editor/`.
  - Move or merge `…/visual/*` and `…/insert/*` tests into here where
    appropriate.
- Rename `…/eval/` to `…/vimscript/`.
  - Move `…/viml/*` into here also.

* test(reorg): insert/* => editor/mode_insert_spec.lua
* test(reorg): cmdline/* => editor/mode_cmdline_spec.lua
* test(reorg): eval core tests => eval_spec.lua

fix: prevent K_EVENT from stopping Select mode CTRL-O #15688

2021-09-17T13:17:51+00:00

When using Goneovim, Select mode `CTRL-O` returns back to Select mode
immediately (even with `--clean`). Neovim TUI (with some plugins) also randomly
returns to Select mode even if no keys are pressed when using `CTRL-O` in Select
mode.

refactor(tests): use assert_alive() #15546

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

edit.c: Ensure undo sync when emulating x #11706

2020-01-13T01:09:39+00:00

After PR #8226 an unmapped META key in insert mode behaves like
ESC- (:help i_META).

The behaviour does not fully match, since if - is pressed
manually then since it were pressed manually `gotchars` would be called
on the second  after insert-mode had already been left.

This would mean that `may_sync_undo` (called from `gotchars`) would
call `u_sync(FALSE)` on the second key (since we would be in normal
mode).

This overall means that  behaves differently with
respect to undo than [something] when the [something] makes a
change.

As an example, under `nvim -u NONE`:
ihellou

leaves the buffer empty, while
ihello.u

leaves the buffer with one instance of `hello`.

- Fix by calling u_sync() manually in the new clause under
  `normalchar:` in `insert_handle_key`.
- Update test in tui_spec.lua that accidentally relied on the old behaviour.

normal: Don't exit CTRL-O mode after processing K_EVENT

2019-06-04T11:59:43+00:00

insert-mode: interpret unmapped META as ESC

2018-04-04T01:23:15+00:00

closes #2454
closes #8213
ref #7972

i_CTRL-O: fix :startinsert at end of line (#6963)

2017-07-08T10:50:58+00:00

The gchar_cursor() == NUL check is already done in ins_ctrl_o.
ins_esc changes gchar_cursor() so this if block is probably never
entered.

Issue:

Pressing CTRL-O in insert mode at the end of the line and typing
:startinsert moves the cursor 1 column back, when I expect the cursor
to remain at the end of the line

This is a regression from Vim behavior. Since at least Vim version 7.0,
Vim returns you to insert mode at the end of the line.

091e7d033cbf0f4da068292ce4ac934f1c3dd91e is the first bad neovim commit

Steps to reproduce using `nvim -u NORC`:
`aaaa:startinsert`

Fixes #6962

ops: fix i with multi-byte text (#6524)

2017-04-15T09:19:40+00:00

edit.c: CTRL-SPC: Insert previously-inserted text. #6090

2017-02-28T00:16:18+00:00

Default Vim behavior of i_CTRL- is to insert the last-inserted
text and exit insert mode. :help i_CTRL-@

Before this commit that did not happen because insert_handle_key()
checks for NUL instead of checking for ' ' with a CTRL `mod_mask`.

I'm leaving the check for NUL despite the fact that at the moment that
key is never seen when using the terminal UI (not for C-Space, nor C-@).
This is because I assume it's still allowed for other front-ends to pass
NUL, but at the moment the terminal UI isn't.