Mercurial > emacs
view BUGS @ 69714:7ff38193167f
Use clipboard-kill-region, clipboard-kill-ring-save, and
clipboard-yank instead of undo, kill-region, and
menu-bar-kill-ring-save respectively. In MH-Letter mode, move
save-buffer and mh-fully-kill-draft icons in front of
mh-compose-insertion to be consistent with other mailers, such as
Evolution. In MH-Folder mode, move vanilla reply icon to the left of
the other reply icons. Use mail/inbox icon instead of mail, next-page
instead of page-down, delete instead of close, mail/move instead of
mail/refile, data-save instead of execute, mail/flag-for-followup
instead of highlight, contact instead of mail/alias, open instead of
fld-open, zoom-out instead of widen.
author | Bill Wohler <wohler@newt.com> |
---|---|
date | Tue, 28 Mar 2006 19:19:38 +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.