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