Mercurial > emacs
view BUGS @ 104984:b4987ada532f
(epg-make-context): Add autoload cookie.
(epg-list-keys, epg-cancel, epg-start-decrypt, epg-decrypt-file)
(epg-decrypt-string, epg-start-verify, epg-verify-file)
(epg-verify-string, epg-start-sign, epg-sign-file)
(epg-sign-string, epg-start-encrypt, epg-encrypt-file)
(epg-encrypt-string, epg-start-export-keys)
(epg-export-keys-to-file, epg-export-keys-to-string)
(epg-start-import-keys, epg-import-keys-from-file)
(epg-import-keys-from-string, epg-start-receive-keys)
(epg-receive-keys, epg-import-keys-from-server)
(epg-start-delete-keys, epg-delete-keys, epg-start-sign-keys)
(epg-sign-keys, epg-start-generate-key)
(epg-generate-key-from-file, epg-generate-key-from-string): Remove
autoload cookie.
author | Daiki Ueno <ueno@unixuser.org> |
---|---|
date | Sat, 12 Sep 2009 14:58:55 +0000 |
parents | fb8bf24d2eb9 |
children | ac52af4a044c |
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-p in Emacs) to make sure it isn't a known issue.