Mercurial > emacs
view BUGS @ 99515:9b767bc53027
* international/mule.el (autoload-coding-system, with-category-table)
(ctext-non-standard-encodings-alist): Fix typos in docstrings.
(coding-system-equal, set-buffer-process-coding-system): Doc fixes.
(set-buffer-file-coding-system, revert-buffer-with-coding-system)
(set-file-name-coding-system, ctext-pre-write-conversion)
(auto-coding-functions, find-auto-coding, modify-coding-system-alist):
Reflow docstrings.
(charset-list, set-coding-priority): Remove redundant obsolescence info.
(charset-id, charset-bytes, make-coding-system): Add obsolescence info.
(char-valid-p): Define with `define-obsolete-function-alias'.
* textmodes/artist.el (artist-mode): Fix typos in docstring.
author | Juanma Barranquero <lekktu@gmail.com> |
---|---|
date | Wed, 12 Nov 2008 18:39:08 +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.