Ajit Thakkar wrote: > I was too quick to say the problems disappeared. > > With 32-bit gvim 7.3.1182 and later, on 64-bit Win 7 SP1, a hang is > often obtained with the simplest of procedures: > > gvim -u NONE a.txt > Make any edit > :w > > It happens in many, but not all, of the subdirectories associated with > my user identity, ie at a level below c:\users\ajit > For example, there is no such problem in the TEMP directory > c:\users\ajit\AppData\Local\Temp > > In a different subdirectory, this procedure gave me an > E293: block was not locked > Then trying :w again led to a hang. > > The exe was compiled with features=normal using a MinGW version of gcc > 4.8.0 > > There were no such problems with gvim 7.3.1181 or earlier to which I > have reverted.
Does this change when you manually change the value of 'backupcopy'? Since you say the problem happens when using ":w" it should. I actually don't see why a wrong value of 'backupcopy' causes a hang. -- hundred-and-one symptoms of being an internet addict: 222. You send more than 20 personal e-mails a day. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
