]> code.delx.au - gnu-emacs/blob - nt/README
(Init File): Say explicitly that site-start.el is also searched along
[gnu-emacs] / nt / README
1 Emacs for Windows NT/2000 and Windows 95/98/ME
2
3 This directory contains support for compiling and running GNU Emacs on
4 Windows NT, Windows 95, and their successors. This port supports all
5 of the major functionality of the Unix version, including
6 subprocesses, windowing features (fonts, colors, scroll bars, multiple
7 frames, etc.), and networking support.
8
9 Precompiled distributions are also available; ftp to
10
11 ftp://ftp.gnu.org/gnu/windows/emacs/latest/
12
13 for the latest precompiled distributions.
14
15 * Building and installing
16
17 See the INSTALL file in this directory for detailed instructions on
18 building and installing Emacs on your system.
19
20 * Further information
21
22 There is a web page that serves as a FAQ at:
23
24 http://www.gnu.org/software/emacs/windows/ntemacs.html
25
26 There is also a mailing list for discussing issues related to this
27 port of Emacs. For information about the list, send a message to
28 ntemacs-users-request@cs.washington.edu with the word "info" in the
29 *body* of the message. To subscribe to the list, send a message to
30 the same address with the word "subscribe" in the body of the message;
31 similarly, to unsubscribe from the list, send a message with the word
32 "unsubscribe" in the message body.
33
34 Another valuable source of information and help which should not be
35 overlooked is the various Usenet news groups dedicated to Emacs.
36 These are particuarly good for help with general issues which aren't
37 specific to the Windows port of Emacs. The main news groups to use
38 for seeking help are:
39
40 gnu.emacs.help
41 comp.emacs
42
43 There are also fairly regular postings and announcements of new or
44 updated Emacs packages on this group:
45
46 gnu.emacs.sources
47
48 You are also always welcome to send me mail directly. If you don't
49 hear from me immediately, however, don't worry; it sometimes takes me
50 a few days (or longer) to get to all of my mail regarding Emacs.
51
52 * Reporting bugs
53
54 If you encounter a bug in this port of Emacs, we would like to hear
55 about it. First check the file etc/PROBLEMS and the FAQ on the web
56 page above to see if the bug is already known and if there are any
57 workarounds. If not, then check whether the bug has something to do
58 with code in your .emacs file, e.g. by invoking Emacs with the "-q
59 --no-site-file" options.
60
61 If you decide that it is a bug in Emacs that might be specific to the
62 Windows port, send a message to the ntemacs-users@cs.washington.edu
63 mailing list describing the bug, the version of Emacs that you are
64 using, and the operating system that you are running on (Windows NT,
65 95 or 98 including service pack level if known). If the bug is
66 related to subprocesses, also specify which shell you are using (e.g.,
67 include the values of `shell-file-name' and `shell-explicit-file-name'
68 in your message).
69
70 If you think the bug is not specific to the Windows port of Emacs,
71 then it is better to mail the bug report to bug-gnu-emacs@gnu.org so
72 that it will be seen by the right people. If Emacs has been set up to
73 send mail, you can use the command M-x report-emacs-bug to create and
74 send the bug report, but in some cases there is a function to report
75 bugs in a specific package; e.g. M-x gnus-bug for Gnus, M-x
76 c-submit-bug-report for C/C++/Java mode, etc.