delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mailnull set sender to djgpp-bounces using -f |
Date: | Sun, 27 Jan 2002 10:33:57 +0200 (IST) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
X-Sender: | eliz AT is |
To: | Pavol Juhas <juhas AT seas DOT upenn DOT edu> |
cc: | djgpp AT delorie DOT com |
Subject: | Re: vim (dos32) hangs under djgpp bash |
In-Reply-To: | <3C539FD2.F493B6DA@seas.upenn.edu> |
Message-ID: | <Pine.SUN.3.91.1020127103310.14549A-100000@is> |
MIME-Version: | 1.0 |
Reply-To: | djgpp AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On Sun, 27 Jan 2002, Pavol Juhas wrote: > The crash of repeated "vim -c q" never occured when invoked via make, I > saw it only after running from bash. Please try from Less as well. It is very important to understand whether only Bash has this problem. > I checked the source code of vim, indeed there are calls to int86() > and __dpmi_yield() in os_msdos.c. I tried to comment out the single > call to __dpmi_yield() and recompile, but it did not help. > I guess that leaves int86() as another option to check. What functions of which interrupts does vim call via int86? Also, what version of Bash do you use?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |