summaryrefslogtreecommitdiff
path: root/admin/nt/README.W32
diff options
context:
space:
mode:
authorAndrew Innes <andrewi@gnu.org>2003-04-22 10:50:52 +0000
committerAndrew Innes <andrewi@gnu.org>2003-04-22 10:50:52 +0000
commit7ee43737e4d1267227ef8ee73ad5c0267e676726 (patch)
tree400e8d9e934c491db3b58101757c773f9a7a3417 /admin/nt/README.W32
parent678c6e62c91675b31065a1e4a10c840cc76dd873 (diff)
downloademacs-7ee43737e4d1267227ef8ee73ad5c0267e676726.tar.gz
Remove personal email address and update wording.
Diffstat (limited to 'admin/nt/README.W32')
-rw-r--r--admin/nt/README.W3218
1 files changed, 9 insertions, 9 deletions
diff --git a/admin/nt/README.W32 b/admin/nt/README.W32
index 2569cd37f20..a3435541d7e 100644
--- a/admin/nt/README.W32
+++ b/admin/nt/README.W32
@@ -1,10 +1,10 @@
- Emacs for Windows NT and Windows 95/98/2000/XP
+ Emacs for Windows
This README file describes how to set up and run a precompiled version
- of GNU Emacs for Windows NT and Windows 95/98/2000/XP. This
+ of GNU Emacs for Windows NT/2000/XP and Windows 95/98/Me. This
distribution can be found on the ftp.gnu.org server and its mirrors:
- ftp://ftp.gnu.org/gnu/windows/emacs/latest/
+ ftp://ftp.gnu.org/gnu/windows/emacs/
This server contains other distributions, including the full Emacs
source distribution and the lisp source distribution, as well as older
@@ -169,16 +169,16 @@
invoking Emacs with the "-q --no-site-file" options.
If you decide that it is a bug in Emacs that might be specific to the
- Windows port, send a message to the ntemacs-users@cs.washington.edu
+ Windows port, send a message to the "help-emacs-windows@gnu.org"
mailing list describing the bug, the version of Emacs that you are
using, and the operating system that you are running on (Windows NT,
- 2000, 95 or 98 including service pack level if known). If the bug is
- related to subprocesses, also specify which shell you are using (e.g.,
- include the values of `shell-file-name' and `shell-explicit-file-name'
- in your message).
+ 2000, 95, 98, etc. including service pack level if known). If the bug
+ is related to subprocesses, also specify which shell you are using
+ (e.g., include the values of `shell-file-name' and
+ `shell-explicit-file-name' in your message).
If you think the bug is not specific to the Windows port of Emacs,
- then it is better to mail the bug report to bug-gnu-emacs@gnu.org so
+ then it is better to mail the bug report to "bug-gnu-emacs@gnu.org" so
that it will be seen by the right people. If Emacs has been set up to
send mail, you can use the command M-x report-emacs-bug to create and
send the bug report, but in some cases there is a function to report