Mercurial > emacs
view BUGS @ 60239:bbe4bd573f0c
Revision: miles@gnu.org--gnu-2005/emacs--cvs-trunk--0--patch-128
Merge from gnus--rel--5.10
Patches applied:
* miles@gnu.org--gnu-2005/gnus--rel--5.10--patch-28
- miles@gnu.org--gnu-2005/gnus--rel--5.10--patch-30
Update from CVS
2005-02-24 Reiner Steib <Reiner.Steib@gmx.de>
* lisp/gnus/nnheader.el (nnheader-find-file-noselect): Added doc string.
* lisp/gnus/nnfolder.el (nnfolder-read-folder): Use RAWFILE for
`nnheader-find-file-noselect' to avoid
`large-file-warning-threshold'.
* lisp/gnus/gnus-sum.el (gnus-summary-caesar-message): Apply
`gnus-treat-article' after rotation.
* lisp/gnus/gnus-group.el (gnus-group-clear-data): Mention process/prefix in
doc string.
2005-02-22 Arne J,Ax(Brgensen <arne@arnested.dk>
* lisp/gnus/smime.el (smime-sign-buffer): Signal an error if
`smime-sign-region' fails.
(smime-encrypt-buffer): Signal an error if `smime-encrypt-region'
fails.
author | Miles Bader <miles@gnu.org> |
---|---|
date | Fri, 25 Feb 2005 01:52:09 +0000 |
parents | 8ce686bd7f4f |
children | fb8bf24d2eb9 |
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 C-e in Emacs) to make sure it isn't a known issue.