diff options
| author | Bram Moolenaar <Bram@vim.org> | 2017-06-04 14:58:02 +0200 |
|---|---|---|
| committer | Bram Moolenaar <Bram@vim.org> | 2017-06-04 14:58:02 +0200 |
| commit | 45e5fd135da5710f24a1acc142692f120f8b0b78 (patch) | |
| tree | db3f8e21176d61550e6c7dbb75dc69faf614c272 /src/globals.h | |
| parent | 6e62da3e14d32f76f60d5cc8b267059923842f17 (diff) | |
patch 8.0.0607: after :bwipe + :new bufref might still be validv8.0.0607
Problem: When creating a bufref, then using :bwipe and :new it might get
the same memory and bufref_valid() returns true.
Solution: Add br_fnum to check the buffer number didn't change.
Diffstat (limited to 'src/globals.h')
| -rw-r--r-- | src/globals.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/globals.h b/src/globals.h index 1d67b0d7af..7bc5471769 100644 --- a/src/globals.h +++ b/src/globals.h @@ -385,7 +385,7 @@ EXTERN int keep_filetype INIT(= FALSE); /* value for did_filetype when /* When deleting the current buffer, another one must be loaded. If we know * which one is preferred, au_new_curbuf is set to it */ -EXTERN bufref_T au_new_curbuf INIT(= {NULL COMMA 0}); +EXTERN bufref_T au_new_curbuf INIT(= {NULL COMMA 0 COMMA 0}); /* When deleting a buffer/window and autocmd_busy is TRUE, do not free the * buffer/window. but link it in the list starting with |