Re: responsiveness issues when editing buffers loaded from mapped network drives

I found a remark on a web page that seems to indicate that gvim behaves differently that vim (running in a terminal) because it will automatically check whether the file on the disk has changed even when the :checktime command is not explicitly invoked. (That remark is at the very top of the web page.)

https://vim.fandom.com/wiki/Have_Vim_check_automatically_if_the_file_has_changed_externally 

Who thought that it was a good idea to hard-wire that behavior in gvim?

On Tuesday, August 18, 2020 at 2:51:21 PM UTC-6 Aaron Bohannon wrote:

Hi,

I'm using gvim (v.8.2) on Windows. Most of the files that I need to edit are stored on a remote server, but I am opening them directly as "local files" through a mapped network drive. Typically, it takes vim 3-5 seconds to open or save one of those files, which comes as no surprise to me. However, unfortunately, vim also responds *very* slowly whenever I try to change between the tabs or windows containing the buffers associated with files on the network drive. And, in fact, even when I'm not switching between the buffers, vim will sometimes hang for a few seconds seemingly for no reason. Why would vim exhibit these responsiveness issues? I would presume that the responsiveness issues arise as a result of vim trying to make network requests. However, I see no real need for vim to make network requests other than when the buffer is opened or saved, and I would like to know how to prevent it from doing so.

I configured vim so that all swap, backup, and undo files are stored on the local disk:

set directory=~/vimfiles/swp//

set backupdir=~/vimfiles/backup//

set undodir=~/vimfiles/undo//

However, I am pretty sure that one reason that vim is making network requests is to check whether the file on disk has changed since it was last loaded. And, in fact, gvim *does* spontaneously alert me when it thinks that file on disk has been changed by another user. So, gvim *must* be making network requests to do that. Now, I was under the impression that vim only makes these checks (before an attempt to save the file) when the :checktime command is run. So, I searched the output of the :autocmd command for any reference to the :checktime command, but I could find none.

So, why is gvim checking whether the file on disk has been changed? How do I stop it from doing that? And are there any other causes for network requests that I ought to know about?

- Aaron

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/57237ac7-9f17-4440-92f2-820941fbe5fbn%40googlegroups.com.