Mail Archives: djgpp/2002/01/25/17:02:50
Martin Stromberg (eplmst AT lu DOT erisoft DOT se) wrote:
> PAVOL JUHAS (juhas AT blue DOT seas DOT upenn DOT edu) wrote:
> : I have a frequent problems with Win98 getting frozen, when using vim
> : (version 6.0 for dos32 djgpp) under djgpp2.03 bash (ver.2.04.7). The
> : system gets completely non-responding and the only way out is to restart
> : the computer. These crashes happen quite randomly, usually while
> : exiting vim. I found a reliable way of reproducing them by running
> : vim -c q; vim -c q
> : This problem does not appear with vimd32 under ordinary dos box,
> : neither with MS-Win 32bit console vim under bash.
> : A relevant usenet post seems to be
> : http://groups.google.com/groups?hl=en&threadm=Pine.GSO.3.96.980827095958.1201A-100000%40rtbsci146s
> : however it is not clear to me how to fix the problem.
> That post is very old and that problem should be corrected long ago,
> but I'm not sure.
> Try running in plain DOZE (both outside bash and within) and see if it
> crashes. If it does post the crash message.
> Alternatively there were recently (weeks or a month ago) a person
> having vim crashing for him, so there were/are definitely a bug in
> vim. Perhaps he can give you information how to find a patched vim.
I am not sure if this is a bug in vim, bash or most likely windows.
However the crashes occur when I use djgpp vim with djgpp bash. Say, I
have a junk.bat file of 10 "vim -c q" lines. If I run it under
command.com, it works, but "source junk.bat" in djgpp bash would freeze
the system. If I used win32 console version of vim, it would work in
both cases. I cannot provide any crash message, since the system gets
completely frozen.
Pavol
- Raw text -