0

I observed that in the recent update for Vim, specifically vim 9.0.1420, it is now possible to create a text file, open it, and then open the same file through another terminal window without encountering the familiar warning message related to .swp files. This message was previously displayed before the update and helped prevent editing an already opened file. Would anybody help me (scritpnames test, etc) to narrow down the cause of this problem? Thank you.

Vivian De Smedt
  • 16,336
  • 3
  • 18
  • 37
DavidC.
  • 101
  • 1
  • I can't repro on 9.0.1450. – muru Apr 20 '23 at 03:16
  • "Would anybody help me (scritpnames test, etc) to narrow down the cause of this problem?" Well, why don't you get ahead and do all that right from the bat? – romainl Apr 20 '23 at 05:22
  • Welcome to Vim! Can you reproduce the problem when you start Vim with vim -u NONE -i NONE? Can you reproduce the problem with vim --clean? – Vivian De Smedt Apr 20 '23 at 06:26
  • @VivianDeSmedt Thanks. If on one terminal I open vim -u NONE test.txt and through another terminal window vim -u NONE test.txt , I can see the .swp warning. Same with vim --clean test.txt. Could you help me to narrow down where the problem is? Super, many thanks – DavidC. Apr 20 '23 at 07:10
  • vim --clean starts Vim without plugins. The "problem" is probably with one of your plugin. My advice would be to do some kind of binary search (disable half of them, disable the other half, ...) to find the culprit. – Vivian De Smedt Apr 20 '23 at 08:52
  • How to debug my vimrc – D. Ben Knoble Apr 20 '23 at 13:46

0 Answers0