Mercurial > emacs
view BUGS @ 80214:062c5adc0b00
(gdb-pc-address, gdb-source-file-list, gdb-cpp-define-alist-program,
gdb-mouse-jump, gdb-get-buffer-create, gdb-debug-log,
gdb-set-gud-minor-mode-existing-buffers-1): Fix typos in docstrings.
(gdb-pending-triggers): Reflow docstring.
(gdb, gdb-init-1): Fix typos in docstrings of gud-def definitions.
author | Juanma Barranquero <lekktu@gmail.com> |
---|---|
date | Tue, 26 Feb 2008 02:01:49 +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.