neovim/test/functional/legacy/arglist_spec.lua
bfredl e61228a214 fix(tests): needing two calls to setup a screen is cringe
Before calling "attach" a screen object is just a dummy container for
(row, col) values whose purpose is to be sent as part of the "attach"
function call anyway.

Just create the screen in an attached state directly. Keep the complete
(row, col, options) config together. It is still completely valid to
later detach and re-attach as needed, including to another session.
2024-11-14 12:40:57 +01:00

52 lines
2.0 KiB
Lua

-- Test argument list commands
local t = require('test.testutil')
local n = require('test.functional.testnvim')()
local Screen = require('test.functional.ui.screen')
local clear, command, eq = n.clear, n.command, t.eq
local expect_exit = n.expect_exit
local feed = n.feed
local pcall_err = t.pcall_err
describe('argument list commands', function()
before_each(clear)
it('quitting Vim with unedited files in the argument list throws E173', function()
command('set nomore')
command('args a b c')
eq('Vim(quit):E173: 2 more files to edit', pcall_err(command, 'quit'))
end)
it(':confirm quit with unedited files in arglist', function()
local screen = Screen.new(60, 6)
command('set nomore')
command('args a b c')
feed(':confirm quit\n')
screen:expect([[
|
{1:~ }|
{3: }|
:confirm quit |
{6:2 more files to edit. Quit anyway?} |
{6:[Y]es, (N)o: }^ |
]])
feed('N')
screen:expect([[
^ |
{1:~ }|*4
|
]])
feed(':confirm quit\n')
screen:expect([[
|
{1:~ }|
{3: }|
:confirm quit |
{6:2 more files to edit. Quit anyway?} |
{6:[Y]es, (N)o: }^ |
]])
expect_exit(1000, feed, 'Y')
end)
end)