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)

  • 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 1:38

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.