view BUGS @ 67934:83b7f7a9b7c9

(flymake-copy-buffer-to-temp-buffer): Simplify. (flymake-parse-output-and-residual): Remove `source-buffer' argument. (flymake-process-filter): Switch to buffer before calling it instead. (flymake-post-syntax-check, flymake-highlight-err-lines) (flymake-delete-own-overlays, flymake-parse-err-lines) (flymake-start-syntax-check, flymake-start-syntax-check-process) (flymake-count-lines, flymake-parse-residual): Remove constant buffer argument. (flymake-start-syntax-check-for-current-buffer): Remove. Update callers to use flymake-start-syntax-check instead. (flymake-display-err-menu-for-current-line): Remove unused var `mouse-pos'. (flymake-restore-formatting): Comment out unused function. (flymake-report-status, flymake-report-fatal-status): Remove buffer argument, use current-buffer instead. Update callers.
author Stefan Monnier <monnier@iro.umontreal.ca>
date Fri, 30 Dec 2005 17:28:30 +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.