Mercurial > emacs
view BUGS @ 96858:d8dd5d59051a
* term/ns-win.el: Standardize references to "Nextstep" in
comments, messages, and docstrings.
(ns-handle-args, x-parse-geometry)
(ns-extended-platform-support-mode, x-setup-function-keys)
(ns-select-overlay, ns-unselect-line, ns-yes-or-no-p)
(ns-set-pasteboard, ns-scroll-bar-move, ns-defined-colors)
(ns-initialized, ns-initialize-window-system): Doc fixes.
author | Chong Yidong <cyd@stupidchicken.com> |
---|---|
date | Mon, 21 Jul 2008 16:23:35 +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.