view BUGS @ 104395:df3d3d6c4426

* net/newst-treeview.el (newsticker-groups-filename): * net/newst-backend.el (newsticker-cache-filename): * speedbar.el (speedbar-update-speed, speedbar-navigating-speed) (speedbar-ignored-path-expressions, speedbar-ignored-path-regexp) (speedbar-add-ignored-path-regexp, speedbar-line-path) (speedbar-buffers-line-path, speedbar-path-line) (speedbar-buffers-line-path): * epg.el (epg-passphrase-callback-function, epg-start-sign-keys,epg-sign-keys): * epa.el (epa-display-verify-result): * progmodes/pascal.el (pascal-outline): Add version of obsolescence.
author Stefan Monnier <monnier@iro.umontreal.ca>
date Fri, 21 Aug 2009 14:59:49 +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.