neovim

commit 45c23a757c6fc601a76a92f052f55eb3ed469364
parent 52f00a6c4d84a13a85ff265a5c59c92795d1b333
Author: zeertzjq <zeertzjq@outlook.com>
Date:   Fri, 26 Aug 2022 20:18:02 +0800

vim-patch:9.0.0275: BufEnter not triggered when using ":edit" in "nofile" buffer

Problem:    BufEnter not triggered when using ":edit" in "nofile" buffer.
Solution:   Let readfile() return NOTDONE. (closes vim/vim#10986)
https://github.com/vim/vim/commit/a9b5b85068b2fcb1c01ea20524e227bcad579ceb

Diffstat:
M
src/nvim/fileio.c
 | 
2
+-
M
src/nvim/testdir/test_autocmd.vim
 | 
12
+++++++++++-

2 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/src/nvim/fileio.c b/src/nvim/fileio.c
@@ -337,7 +337,7 @@ int readfile(char *fname, char *sfname, linenr_T from, linenr_T lines_to_skip,
     curbuf->b_op_start = orig_start;
 
     if (flags & READ_NOFILE) {
-      return FAIL;
+      return NOTDONE;  // so that BufEnter can be triggered
     }
   }
 
diff --git a/src/nvim/testdir/test_autocmd.vim b/src/nvim/testdir/test_autocmd.vim
@@ -599,9 +599,19 @@ func Test_BufEnter()
   " On MS-Windows we can't edit the directory, make sure we wipe the right
   " buffer.
   bwipe! Xdir
-
   call delete('Xdir', 'd')
   au! BufEnter
+
+  " Editing a "nofile" buffer doesn't read the file but does trigger BufEnter
+  " for historic reasons.
+  new somefile
+  set buftype=nofile
+  au BufEnter somefile call setline(1, 'some text')
+  edit
+  call assert_equal('some text', getline(1))
+
+  bwipe!
+  au! BufEnter
 endfunc
 
 " Closing a window might cause an endless loop