fix(events): always allow some events to be nested (#32706)

Always allow the following four events to be nested, as they may contain
important information, and are triggered on the event loop, which may be
processed by a blocking call inside another autocommand.

- ChanInfo
- ChanOpen
- TermRequest
- TermResponse

There are some other events that are triggered on the event loop, but
they are mostly triggered by user actions in a UI client, and therefore
not very likely to happen during another autocommand, so leave them
unchanged for now.

1 files changed, 1 insertions, 1 deletions

diff --git a/src/nvim/api/ui.c b/src/nvim/api/ui.c
index 7aa4cf4576..aa9dc1098e 100644
--- a/src/nvim/api/ui.c
+++ b/src/nvim/api/ui.c
@@ -510,7 +510,7 @@ void nvim_ui_term_event(uint64_t channel_id, String event, Object value, Error *
 
     MAXSIZE_TEMP_DICT(data, 1);
     PUT_C(data, "sequence", value);
-    apply_autocmds_group(EVENT_TERMRESPONSE, NULL, NULL, false, AUGROUP_ALL, NULL, NULL,
+    apply_autocmds_group(EVENT_TERMRESPONSE, NULL, NULL, true, AUGROUP_ALL, NULL, NULL,
                          &DICT_OBJ(data));
   }
 }