[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [vile] Console hang on exit (Win32)

From: Thomas Dickey
Subject: RE: [vile] Console hang on exit (Win32)
Date: Sun, 21 Feb 2010 11:06:12 -0500 (EST)

On Sun, 21 Feb 2010, Rick Sladkey wrote:

First, I'm happy to report that vile compiles cleanly out of the box
using the Visual Studio 64-bit compiler.  Just set up the environment

        "c:\Program Files (x86)\Microsoft Visual Studio 

and build as usual.  Now I can edit those 6 gigabyte text files that
have been eluding me...

6Gb might be stressful...

Seriously though, the per-line overhead does keep vile from using all of memory for the file's contents.

As far as my origin issue, I've fixed the console hang on exit and the
problem was fairly straightforward:

thanks (I'm sidetracked into mawk at the moment - this helps to close out changes toward 9.7zc).

--- ..\orig\vile-9.7zb/main.c   2010-01-29 20:09:13.000000000 -0500
+++ main.c      2010-02-21 01:50:54.793200500 -0500
@@ -1244,6 +1244,9 @@
+    term.close();
#if DISP_X11
    term.close();               /* need this if $xshell left subprocesses */

It turns out that ntconio_close was never being called at all.  In fact
this fixes both of the console hangs I reported.

I also have a patch to prevent an fstat assert when compiled for debugging:

--- ..\orig\vile-9.7zb/fileio.c 2009-10-05 21:02:15.000000000 -0400
+++ fileio.c    2010-02-21 00:51:24.936250500 -0500
@@ -459,8 +459,12 @@
     * the symbols for portability.
#ifndef X_OK
+#if defined(_WIN32)
+#define X_OK 0
#define X_OK 1
#ifndef W_OK
#define W_OK 2

Thomas E. Dickey

reply via email to

[Prev in Thread] Current Thread [Next in Thread]