1# Id: README,v 8.153 2001/04/30 09:31:12 skimo Exp (Berkeley) Date: 2001/04/30 09:31:12 2 3This is version 1.81.6 (2007-11-18) of nex/nvi, a reimplementation of the ex/vi 4text editors originally distributed as part of the Fourth Berkeley 5Software Distribution (4BSD), by the University of California, Berkeley. 6 7The directory layout is as follows: 8 9 LICENSE ....... Copyright, use and redistribution information. 10 README ........ This file. 11 build.unix .... UNIX build directory. 12 catalog ....... Message catalogs; see catalog/README. 13 cl ............ Vi interface to the curses(3) library. 14 clib .......... C library replacement source code. 15 common ........ Code shared by ex and vi. 16 db ............ A stripped-down, replacement db(3) library. 17 dist .......... Various files used to build the vi distribution. 18 docs .......... Ex/vi documentation, both current and historic. 19 docs/README ... Documentation overview. 20 docs/edit ..... Edit: A tutorial. 21 docs/exref .... Ex Reference Manual -- Version 3.7. 22 docs/vi.man ... UNIX manual page for nex/nvi. 23 docs/vi.ref ... Nex/nvi reference manual. 24 docs/vitut .... An Introduction to Display Editing with Vi. 25 ex ............ Ex source code. 26 gtk ........... Vi gtk application. 27 include ....... Replacement include files. 28 ip ............ Library interface to vi: vi side. 29 ipc ........... Library interface to vi: application side. 30 motif ......... Vi motif application. 31 motif_l ....... Motif library interface to vi. 32 perl_api ...... Perl scripting language support. 33 perl_scripts .. Perl scripts. 34 regex ......... POSIX 1003.2 regular expression library. 35 tcl_api ....... Tcl scripting language support. 36 tcl_scripts ... Tcl scripts. 37 vi ............ Vi source code. 38 39To build DB for a UNIX platform: 40 41 cd build.unix 42 ../dist/configure 43 make 44 45To build multiple UNIX versions of DB in the same source tree, create 46a new directory then configure and build. 47 48 mkdir build.bsdos3.0 49 cd build.bsdos3.0 50 ../dist/configure 51 make 52 53For additional information about building DB for UNIX platforms, the 54description of possible configuration options and other information 55on DB configuration and build issues, see the file build.unix/README. 56 57Bug fixes and updated versions of this software will periodically be made 58available. For more information, as well as a list of Frequently Asked 59Questions, see: 60 61 http://www.bostic.com/vi 62 63To ask questions about vi, report vi problems, request notification of 64future releases and/or bug fixes, or to contact the authors for any 65reason, please send email to: 66 67 bostic@bostic.com 68 69=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 70o This software is several years old and is the product of many folks' work. 71 72 This software was originally derived from software contributed to 73 the University of California, Berkeley by Steve Kirkendall, the 74 author of the vi clone elvis. Without his work, this work would 75 have been far more difficult. 76 77 IEEE POSIX 1003.2 style regular expression support is courtesy of 78 Henry Spencer, for which I am *very* grateful. 79 80 Elan Amir did the original 4BSD curses work that made it possible 81 to support a full-screen editor using curses. 82 83 George Neville-Neil added the Tcl interpreter, and the initial 84 interpreter design was his. 85 86 Sven Verdoolaege added the Perl interpreter. 87 88 Rob Mayoff provided the original Cscope support. 89 90o Many, many people suggested enhancements, and provided bug reports and 91 testing, far too many to individually thank. 92 93o From the original vi acknowledgements, by William Joy and Mark Horton: 94 95 Bruce Englar encouraged the early development of this display 96 editor. Peter Kessler helped bring sanity to version 2's 97 command layout. Bill Joy wrote versions 1 and 2.0 through 2.7, 98 and created the framework that users see in the present editor. 99 Mark Horton added macros and other features and made the editor 100 work on a large number of terminals and Unix systems. 101 102o And... 103 The financial support of UUNET Communications Services is gratefully 104 acknowledged. 105