why is b:changedtick never zero?

Asked Jan 15 '18 at 19:37

Active Jan 15 '18 at 19:37

Viewed 124 times

As the Title states b:changedtick is never zero. No plugin or special setting seems to be involved.

Even :

vim -u NONE -U NONE
:echo b:changedtick

returns a value != 0

The same happens if I start vim with a filename (no matter if the file exists)

asked Jan 15 '18 at 19:37

Naumann

1

Seems like a side-effect of the implementation, see e.g. unchanged() and changed() in misc1.c. – Martin Tournoij Jan 15 '18 at 20:43
I see. The file is named misc1 here. I guess b:changedtick does not reliantly reflect the number of changes – Naumann Jan 16 '18 at 01:38

0 Answers0