71301Re: Patch 7.3.1182
- Jun 16, 2013Setting backupcopy=yes does seem to solve the problem, at least on three tries.Without it, the behavior is erratic. Just now, in the last 5 minutes, I got on different occasions an E510, an E222, an E211, and a backup file named yyyy (but all the y's had an umlaut on them) left behind in the current directory.It gives me the impression that some random access to memory is taking place, as if there were an attempt to use an uninitialized value or an array element with an index outside the declared range.--On Sun, Jun 16, 2013 at 9:18 AM, Bram Moolenaar <Bram@...> wrote:Does this change when you manually change the value of 'backupcopy'?
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
> 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
> 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
> There were no such problems with gvim 7.3.1181 or earlier to which I
> have reverted.
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 -- Bram@... -- 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 ///
Ajit Thakkar, PhD, FCIC
Professor of Chemistry
University of New Brunswick
Fredericton, NB, Canada
Editor, Computational & Theoretical Chemistry
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 vim_dev+unsubscribe@....
For more options, visit https://groups.google.com/groups/opt_out.
- << Previous post in topic Next post in topic >>