Known (serious) problems with 8.1: - an incorrect ifdef causes xvile to be linked with vfork rather than fork. This is exercised by the forkOnStartup code. Not all platforms have a working vfork; additionally this could cause data corruption, because the vfork'd process may share data with the parent process (fixed in 8.2). Known (serious) problems with 7.0: - none Known (serious) problems with 6.4: - none Known (serious) problems with 6.3: - search command "?$" resulted in infinite loop Known (serious) problems with 6.2: - changes in 6.1 for macros broke some cases for ~endif/~else logic Known (serious) problems with 6.1: - none Known (serious) problems with 6.0: - vile will not save modified buffers correctly if it is killed. if the editor dies due to a signal (due to a hangup or a bug or by typing "kill PID" to kill the editor from a different terminal) and there are modified buffers, vile will try to save those buffers in /tmp. the patch in "patch-6.0p1" fixes this. applying the work-in-progress patches a, b, and c will also get you that fix, along with other changes that you may not want. - on the NT version of vile, if you type ^C after running at least one shell command, the ^C will kill the editor. the fix for this is to apply the work-in-progress patches vilepatch-6.0a and vilepatch-6.0b. Known (serious) problems with 5.6: - none under UNIX The three following problems are fixed by applying the patchfile vilepatch5.6.p1 to the source before building. The patch is not needed for most UNIX builds. - djgpp-built DOS binaries will still crash if you use the filter operator. the provided binary (vil56dos.zip) is built with Watcom. - there's an ifdef problem under some VMS builds -- apply the 5.6a and 5.6b patches from ../work-in-progress to fix it. i wouldn't apply any more than that without reading the caution in that directory _Very_ carefully. - vile-manfilt may fail sometimes due to an uninitialized reference. Known (serious) problems with 5.5: - the filtering operator is broken under the DJGPP version of DOS. it will cause a CRASH if you use it. the unix version seems safe. i've replaced the djgpp DOS binary in vil55dos.zip with a Watcom binary. - wrapmargin doesn't work right unless autoindent is on too. - resolve-links mode and view-on-readonly mode don't work together in the presence of symlinks. Known (serious) problems with 5.2: -none so far. some people have reported configuration problems under various OSes. please let me know if vile doesn't install pretty easily for you.