1 Emacs for Windows NT and Windows 95
3 This directory contains support for compiling and running GNU Emacs on
4 Windows NT and Windows 95. This port supports all of the major
5 functionality of the Unix version, including subprocesses, windowing
6 features (fonts, colors, scroll bars, multiple frames, etc.), and
9 Precompiled distributions are also available; ftp to
11 ftp://ftp.cs.washington.edu/pub/ntemacs/latest
13 for the latest precompiled distributions.
17 To compile Emacs, you will need a Microsoft C compiler package. For
18 NT, this can be any of the SDK compilers from NT 3.1 and up, Microsoft
19 Visual C++ for NT (versions 1.0 and up), or Microsoft Visual C++
20 (versions 2.0 and up). For Windows 95, this can be Microsoft Visual
21 C++ versions 2.0 and up.
23 * Building and installing
25 See the INSTALL file in this directory for detailed instructions on
26 building and installing Emacs on your system.
30 If you have access to the World Wide Web, I would recommend pointing
31 your favorite web browser to the document (if you haven't already):
33 http://www.cs.washington.edu/homes/voelker/ntemacs.html
35 This web document serves as a FAQ and a source for further information
36 about the port and related software packages.
38 There is also a mailing list for discussing issues related to this
39 port of Emacs. For information about the list, send a message to
40 ntemacs-users-request@cs.washington.edu with the word "info" in the
41 *body* of the message. To subscribe to the list, send a message to
42 the same address with the word "subscribe" in the body of the message;
43 similarly, to unsubscribe from the list, send a message with the word
44 "unsubscribe" in the message body.
46 You are also always welcome to send me mail directly. If you don't
47 hear from me immediately, however, don't worry; it sometimes takes me
48 a few days (or longer) to get to all of my mail regarding Emacs.
52 If you encounter bugs in this port of Emacs, first check the FAQ on
53 the web page above to see if the bug is already known and if there are
54 any workarounds. If not, then I would like to hear about it; either
55 send a bug report to the mailing list, or to me directly (I would
56 recommend sending to the list first).
61 (voelker@cs.washington.edu)