(unlock_buffer): Declare it as void.

[gnu-emacs] / INSTALL

diff --git a/INSTALL b/INSTALL
index d5cfa39a75293c7f7569f147a3a3a18cbb80f106..86d94a7ddf8d6ee990f15123122ca43d682d25b9 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -1,5 +1,5 @@
 GNU Emacs Installation Guide
-Copyright (c) 1992, 1994, 1996 Free software Foundation, Inc.
+Copyright (c) 1992, 1994, 1996, 1997 Free software Foundation, Inc.
 
    Permission is granted to anyone to make or distribute verbatim copies
    of this document as received, in any medium, provided that the
@@ -38,8 +38,12 @@ build Emacs again and install it again.
 The intlfonts distribution contains X11 fonts that Emacs needs in
 order to display international characters.  If you see a non-ASCII
 character appear as a hollow box, that means you don't have a font for
-it.  You might find a font in the intlfonts distribution.  That
-distribution contains its own installation instructions.
+it.  You might find a font in the intlfonts distribution.  If some
+characters don't look right, or appear improperly aligned, a font
+from the intlfonts distribution might look better.
+
+The intlfonts distribution contains its own installation instructions,
+in the intlfonts/README file.
 
 
 BUILDING AND INSTALLATION:
@@ -600,12 +604,7 @@ To unpack Emacs with djtar, type this command:
     djtar -x emacs.tgz
 
 (This assumes that the Emacs distribution is called `emacs.tgz' on
-your system.)  There are a few files in the archive whose names
-collide with other files under the 8.3 DOS naming.  On native MSDOS,
-or if you have set LFN=n on Windows 95, djtar will ask you to supply
-alternate names for these files; you can just press `Enter' when this
-happens (which makes djtar skip these files) because they aren't
-required for MS-DOS.
+your system.)
 
 When unpacking is done, a directory called `emacs-XX.YY' will be
 created, where XX.YY is the Emacs version.  To build and install
@@ -628,8 +627,9 @@ if you run Emacs under MS Windows.
 Emacs on MSDOS finds the lisp, etc and info directories by looking in
 ../lisp, ../etc and ../info, starting from the directory where the
 Emacs executable was run from.  You can override this by setting the
-environment variable HOME; if you do that, the directories lisp, etc
-and info are accessed as subdirectories of the HOME directory.
+environment variables EMACSDATA (for the location of `etc' directory),
+EMACSLOADPATH (for the location of `lisp' directory) and INFOPATH (for
+the location of the `info' directory).
 
 MSDOG is a not a multitasking operating system, so Emacs features such
 as asynchronous subprocesses that depend on multitasking will not