Mercurial > emacs
view BUGS @ 34858:6c93e7d6a930
* message.el (message-setup): Use cons. Suggested by Johan Vromans
<jvromans@squirrel.nl>.
* gnus-topic.el (gnus-topic-create-topic): Use list.
* gnus-vm.el (gnus-summary-save-article-vm): Require gnus-art
before binding gnus-default-article-saver.
* gnus-sum.el (gnus-summary-save-article):
(gnus-summary-pipe-output):
(gnus-summary-save-article-mail):
(gnus-summary-save-article-rmail):
(gnus-summary-save-article-file):
(gnus-summary-write-article-file):
(gnus-summary-save-article-body-file): Ditto.
* gnus-mh.el (gnus-summary-save-article-folder): Ditto.
author | ShengHuo ZHU <zsh@cs.rochester.edu> |
---|---|
date | Sun, 24 Dec 2000 06:36:33 +0000 |
parents | af68d12218d0 |
children | 8ce686bd7f4f |
line wrap: on
line source
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," Please first check the file etc/PROBLEMS (e.g. with C-h P in Emacs) to make sure it isn't a known issue.