1 Emacs for Windows NT/2000 and Windows 95/98/ME
3 Copyright (C) 2001, 2002, 2003, 2004, 2005,
4 2006 Free Software Foundation, Inc.
5 See the end of the INSTALL file in this directory for copying permissions.
7 This directory contains support for compiling and running GNU Emacs on
8 Windows NT, Windows 95, and their successors. This port supports all
9 of the major functionality of the Unix version, including
10 subprocesses, windowing features (fonts, colors, scroll bars, multiple
11 frames, etc.), and networking support.
13 Precompiled distributions are also available; ftp to
15 ftp://ftp.gnu.org/gnu/windows/emacs/latest/
17 for the latest precompiled distributions.
19 * Building and installing
21 See the INSTALL file in this directory for detailed instructions on
22 building and installing Emacs on your system.
26 There is a web page that serves as a FAQ for the Windows port of
27 Emacs (a.k.a. NTEmacs) at:
29 http://www.gnu.org/software/emacs/windows/ntemacs.html
31 There is also a mailing list for discussing issues related to this
32 port of Emacs. For information about the list, see this Web page:
34 http://mail.gnu.org/mailman/listinfo/help-emacs-windows
36 To ask questions on the mailing list, send email to
37 help-emacs-windows@gnu.org. (You don't need to subscribe for that.)
38 To subscribe to the list or unsubscribe from it, fill the form you
39 find at http://mail.gnu.org/mailman/listinfo/help-emacs-windows as
42 Another valuable source of information and help which should not be
43 overlooked is the various Usenet news groups dedicated to Emacs.
44 These are particularly good for help with general issues which aren't
45 specific to the Windows port of Emacs. The main news groups to use
51 There are also fairly regular postings and announcements of new or
52 updated Emacs packages on this group:
58 If you encounter a bug in this port of Emacs, we would like to hear
59 about it. First check the file etc/PROBLEMS and the FAQ on the web
60 page above to see if the bug is already known and if there are any
61 workarounds. If not, then check whether the bug has something to do
62 with code in your .emacs file, e.g. by invoking Emacs with the "-q
63 --no-site-file" options.
65 If you decide that it is a bug in Emacs that might be specific to the
66 Windows port, send a message to the help-emacs-windows@gnu.org
67 mailing list describing the bug, the version of Emacs that you are
68 using, and the operating system that you are running on (Windows NT,
69 95 or 98 including service pack level if known). If the bug is
70 related to subprocesses, also specify which shell you are using (e.g.,
71 include the values of `shell-file-name' and `shell-explicit-file-name'
74 If you think the bug is not specific to the Windows port of Emacs,
75 then it is better to mail the bug report to bug-gnu-emacs@gnu.org so
76 that it will be seen by the right people. If Emacs has been set up to
77 send mail, you can use the command M-x report-emacs-bug to create and
78 send the bug report, but in some cases there is a function to report
79 bugs in a specific package; e.g. M-x gnus-bug for Gnus, M-x
80 c-submit-bug-report for C/C++/Java mode, etc.