view BUGS @ 92111:105ec1146aa7

Finish pdbtrack integration cleanup, settling missing-functions byte compiler warnings appropriately. * progmodes/python.el (python-point): Remove this - beginning-of-line was all that was necessary for `python-pdbtrack-overlay-arrow'. (python-end-of-def-or-class, python-beginning-of-def-or-class) (python-goto-initial-line): Drop these - they were only needed for python-point. (python-comint-output-filter-function): Use condition-case and beginning-of-line directly, instead of python-mode.el functions which require all sorts of baggage. (point-safe): Unnecessary - we're using condition-case directly, instead. (python-execute-file): Include for python-shell, which i'm leaving in keeping despite it being unnecessary for pdb tracking.

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.