Mercurial > vim
comparison src/bufwrite.c @ 22985:d768cdd50602 v8.2.2039
patch 8.2.2039: viminfo is not written when creating a new file
Commit: https://github.com/vim/vim/commit/8e6be34338f13a6a625f19bcef82019c9adc65f2
Author: Bram Moolenaar <Bram@vim.org>
Date: Mon Nov 23 22:01:26 2020 +0100
patch 8.2.2039: viminfo is not written when creating a new file
Problem: Viminfo is not written when creating a new file.
Solution: Set "b_marks_read" in the new buffer. (Christian Brabandt,
closes #7350)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Mon, 23 Nov 2020 22:15:05 +0100 |
parents | e82579016863 |
children | b545334ae654 |
comparison
equal
deleted
inserted
replaced
22984:79eac5f2dad6 | 22985:d768cdd50602 |
---|---|
2577 if (aborting()) // autocmds may abort script processing | 2577 if (aborting()) // autocmds may abort script processing |
2578 retval = FALSE; | 2578 retval = FALSE; |
2579 #endif | 2579 #endif |
2580 } | 2580 } |
2581 | 2581 |
2582 #ifdef FEAT_VIMINFO | |
2583 // Make sure marks will be written out to the viminfo file later, even when | |
2584 // the file is new. | |
2585 curbuf->b_marks_read = TRUE; | |
2586 #endif | |
2587 | |
2582 got_int |= prev_got_int; | 2588 got_int |= prev_got_int; |
2583 | 2589 |
2584 return retval; | 2590 return retval; |
2585 } | 2591 } |