view BUGS @ 90861:4f7df84e666c

(toggle-enable-multibyte-characters, sort-coding-systems, search-unencodable-char): Doc fixes. (default-input-method, input-method-verbose-flag, input-method-highlight-flag): Remove * in defcustom's docstrings. (exit-language-environment-hook, set-default-coding-systems, coding-system-change-eol-conversion, prefer-coding-system, find-multibyte-characters, leim-list-entry-regexp, set-input-method, input-method-exit-on-first-char, princ-list, locale-language-names, locale-charset-language-names, define-char-code-property): Fix typos in docstrings.
author Juanma Barranquero <lekktu@gmail.com>
date Tue, 29 May 2007 00:14:53 +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.