Mercurial > emacs
view BUGS @ 33319:b398f6832863
(gnus-score-load-file): Use expand-file-name.
(gnus-score-find-bnews): Don't concat "".
2000-10-07 09:18:53 ShengHuo ZHU <zsh@cs.rochester.edu>
* gnus-score.el (gnus-score-body): Don't score body when
agent-fetching.
(gnus-score-followup): Don't score followup either.
2000-09-21 16:15:25 ShengHuo ZHU <zsh@cs.rochester.edu>
* gnus-score.el (gnus-score-use-all-scores): New variable.
(gnus-all-score-files): Use it.
2000-09-20 18:33:00 ShengHuo ZHU <zsh@cs.rochester.edu>
* gnus-score.el (gnus-score-find-bnews): Use directory-sep-char.
author | Dave Love <fx@gnu.org> |
---|---|
date | Wed, 08 Nov 2000 20:51:01 +0000 |
parents | 354e0c45cedf |
children | af68d12218d0 |
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,"