Mercurial > emacs
view BUGS @ 88130:363419a0d27c
Commentary: Add text.
History: Add header and mbox item.
Overhaul summary buffer movement.
(rmail-summary-font-lock-keywords): Compress the attribute character
display field by one character.
(rmail-new-summary): Rewrite.
(rmail-make-summary-line-1): Slight rewrite to deal with small changes
in the summary format.
(rmail-make-basic-summary-line): Use the rmail message vector.
(rmail-summary-next-msg): Rewrite.
(rmail-summary-next-labeled-message): Set the summary buffer copy of
the rmail-current-message to force the display to show it.
(rmail-summary-next-same-subject): Rewrite.
(rmail-summary-delete-forward): Remove some questionable code and make
summary buffer movement explicit.
(rmail-summary-mark-deleted): Make sure to reflect the deletion for
the Rmail buffer.
(rmail-summary-deleted-p): Rewrite.
(rmail-summary-undelete-many): Set the summary buffer copy of
the rmail-current-message to force the display to show it.
(rmail-summary-rmail-update): Rewrite.
(rmail-summary-mode-map): Use "B" to send the message body to a
browser; use (rmail-summary-output) instead of
(rmail-summary-output-to-rmail-file). Similarly for the menu item.
(rmail-summary-mouse-goto-msg): Set the summary buffer copy of the
rmail-current-message to force the display to show it.
(rmail-summary-get-message-at-point): New function.
(rmail-summary-goto-msg): Rewrite.
(rmail-summary-expunge, rmail-summary-expunge-and-save,
rmail-summary-get-new-mail, rmail-summary-toggle-header): Rewrite.
(rmail-summary-get-line-count, rmail-summary-get-summary-attributes,
rmail-summary-get-summary, rmail-summary-update-attribute,
rmail-summary-browse-body): New functions.
author | Paul Reilly <pmr@pajato.com> |
---|---|
date | Sat, 15 Feb 2003 17:13:03 +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.