neovim/test/functional/options
Justin M. Keyes 167a2383b9
fix(api): not using TRY_WRAP, generic error messages #31595
Problem:
- API functions using `try_start` directly instead of `TRY_WRAP`, do not
  surface the underlying error message, and instead show generic things
  like "Failed to set buffer".
- Error handling code is duplicated in the API impl, instead of
  delegating to the vim buffer/window handling logic.

Solution:
- Use `TRY_WRAP`.
2024-12-16 04:00:20 -08:00
..
autochdir_spec.lua refactor(test): rename alter_slashes, invert its behavior 2024-09-09 12:23:54 +02:00
belloff_spec.lua fix(tests): needing two calls to setup a screen is cringe 2024-11-14 12:40:57 +01:00
chars_spec.lua fix(tests): needing two calls to setup a screen is cringe 2024-11-14 12:40:57 +01:00
cursorbind_spec.lua fix(tests): needing two calls to setup a screen is cringe 2024-11-14 12:40:57 +01:00
defaults_spec.lua fix(tests): needing two calls to setup a screen is cringe 2024-11-14 12:40:57 +01:00
keymap_spec.lua test: improve test conventions 2024-04-23 18:17:04 +02:00
modified_spec.lua test: improve test conventions 2024-04-23 18:17:04 +02:00
mousescroll_spec.lua test: improve test conventions 2024-04-23 18:17:04 +02:00
num_options_spec.lua test: improve test conventions 2024-04-23 18:17:04 +02:00
shortmess_spec.lua fix(tests): needing two calls to setup a screen is cringe 2024-11-14 12:40:57 +01:00
tabstop_spec.lua test: improve test conventions 2024-04-23 18:17:04 +02:00
winfixbuf_spec.lua fix(api): not using TRY_WRAP, generic error messages #31595 2024-12-16 04:00:20 -08:00