summaryrefslogtreecommitdiff
path: root/BUGS
diff options
context:
space:
mode:
authorDave Love <fx@gnu.org>1999-10-03 15:56:58 +0000
committerDave Love <fx@gnu.org>1999-10-03 15:56:58 +0000
commita4a9692da15ec1531a5075b671b62ebf1f2b9d92 (patch)
tree13d2395598273a1e6667211e29c6d286480d65b6 /BUGS
parentd7f3b2023f6105f04e90791ee19efd5a872ce33a (diff)
#
Diffstat (limited to 'BUGS')
-rw-r--r--BUGS24
1 files changed, 24 insertions, 0 deletions
diff --git a/BUGS b/BUGS
new file mode 100644
index 0000000000..d78f0d71b0
--- /dev/null
+++ b/BUGS
@@ -0,0 +1,24 @@
+If you think you may have found a bug in GNU Emacs, please
+read the Bugs section of the Emacs manual for advice on
+(1) how to tell when to report a bug, and
+(2) how to write a useful bug report and what information
+it needs to have.
+
+There are three ways to read the Bugs section.
+
+(1) In a printed copy of the Emacs manual.
+You can order one from the Free Software Foundation;
+see the file etc/ORDERS. But if you don't have a copy on
+hand and you think you have found a bug, you shouldn't wait
+to get a printed manual; you should read the section right away
+as described below.
+
+(2) With Info. Start Emacs, do C-h i to enter Info,
+then m Emacs RET to get to the Emacs manual, then m Bugs RET
+to get to the section on bugs. Or use standalone Info in
+a like manner. (Standalone Info is part of the Texinfo distribution,
+not part of the Emacs distribution.)
+
+(3) By hand. Do
+ cat info/emacs* | more "+/^File: emacs, Node: Bugs,"
+