Get E948 and E676 error while trying exiting with :wqa.

[alohaia]

Environment

If you are using neovim, just run :checkhealth floaterm and post the content

below.

floaterm: health#floaterm#check
========================================================================
## common
  - INFO: Platform: linux
  - INFO: Nvim: NVIM v0.6.0
  - INFO: Plugin: 399cb86

## terminal
  - OK: Terminal emulator is available

## floating
  - OK: Floating window is available

Configurations related to vim-floaterm in vimrc(i.e. g:floaterm_xxx):

I use Lua to config vim-floaterm:

vim.g.floaterm_keymap_toggle = '<F1>'
vim.g.floaterm_keymap_prev   = '<F2>'
vim.g.floaterm_keymap_next   = '<F3>'
vim.g.floaterm_keymap_new    = '<F4>'
vim.g.floaterm_gitcommit     = 'floaterm'
vim.g.floaterm_autoinsert    = 1
vim.g.floaterm_width         = 0.5
vim.g.floaterm_height        = 0.5
vim.g.floaterm_autoclose     = 1
vim.g.floaterm_title         = 'floaterm: $1/$2'
vim.g.floaterm_wintype       = 'popup'
vim.g.floaterm_position      = 'bottomright'
vim.cmd('hi link FloatermBorder Normal')

Describe your question, feature request, or bug.

When I have at least one floaterm buffer existing and use :wqa command to exit, I got this message:

E948: Job still running
E676: No matching autocommands for acwrite buffer
E948: Job still running
E676: No matching autocommands for acwrite buffer

Here I have two floaterm buffers.

Steps to reproduce

Using the minimal vimrc

set nocompatible
set hidden
set termguicolors
set runtimepath^=~/.config/nvim/vim-floaterm
filetype plugin indent on
syntax on

Steps to reproduce the behavior:

1. Enter NeoVim: LANG=en_US nvim
2. :FloatermNew
3. <C-\\><C-n>
4. :wqa

Actual behaviour

I got message as below and was blocked from exiting.

E948: Job still running                                                                                                                                                      
E676: No matching autocommands for acwrite buffer

Expected behaviour

Exit without any message.

[MaiLunJiye]

It is a neovim terminal bug.

https://github.com/neovim/neovim/issues/14061