"WiggyWare" said: > So my question is: Why does VIM create a file in every directory along > the path of the edited file? Secondly, is there a way to disable this > behavior?
VIM is not creating a file in those directories. In Windows, the CreateFile() API is used to open a file handle, whether opening an existing file or creating a new file. So, file handles to the directories "C:\", then "C:\Documents and Settings", then finally "C:\Documents and Settings\a249261" got opened and closed. All that was done on each file handle was to get a directory listing for a specific file pattern. For instance, under "C:\", the file pattern "Documents and Settings" was queried for; and so on. Maybe all of this is to test for the existence of "C:\Documents and Settings\a249261\.bash_history" (is this the file you were editing?), but in a very inefficient way. Or maybe it is trying to construct a normalized path name. It's hard to say what the purpose is, or where the operations are coming from, from just this information. Using ProcMon, I couldn't actually see any file operations when editing a local file and moving the cursor around. I had done a :runtime plugin/matchparen.vim followed by :DoMatchParen. What are the necessary steps, precisely, starting with vim -u NONE? Craig -- You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php
