Mercurial > emacs
view admin/notes/BRANCH @ 92060:fd85a7810d53
Revise pdbtrack functionality to incorporate advances in python-mode.el.
(I'm doing this python.el checkin with some byte-compiler warnings. These
warnings existed before Nick Roberts or I applied any of the pdbtrack
changes, and look very clearly like preexisting, incomplete adoption of
code from python-mode.el. I'm going to next look at settling those
warnings, though I don't have time for a major reconciliation of the two
python-mode implementations.)
(python-pdbtrack-toggle-stack-tracking): Clarify docstring.
(python-pdbtrack-minor-mode-string): A sign indicating that pdb
tracking is happening.
(python-pdbtrack-stack-entry-regexp): Better recognize stack traces.
(python-pdbtrack-input-prompt): Better recognize PDB prompts.
(add python-pdbtrack-track-stack-file to comint-output-filter-functions):
Tracking is plugged in to all comint buffers once python.el is loaded.
(python-pdbtrack-overlay-arrow): Toggle activation of
`python-pdbtrack-minor-mode-string' in addition to the overlay arrow.
(python-pdbtrack-track-stack-file): Use new
`python-pdbtrack-get-source-buffer' for more flexible access to
debugging source files.
(python-pdbtrack-get-source-buffer): Identify debugging target
buffer according to pdb stack trace, optionally using new
`python-pdbtrack-grub-for-buffer' if file is not locally
available.
(python-pdbtrack-grub-for-buffer): Find most recent python-mode
named buffer, or having function with indicated name.
(python-shell): Remove comint-output-filter-functions hook
addition, it's being done elsewhere. Wrap long line.
author | Ken Manheimer <ken.manheimer@gmail.com> |
---|---|
date | Thu, 21 Feb 2008 22:28:13 +0000 |
parents | 7dd2d0d806e8 |
children | b2b85b22b20e 8080c98e919f |
line wrap: on
line source
This file describes the CVS branch in which it is maintained. Everything below the line is branch-specific. ________________________________________________________________________ This is the "HEAD" branch, otherwise known as the "trunk". Its primary purpose is to accumulate changes that are not yet partitioned into a specific (versioned) release. When people say "use CVS emacs", this is the branch they are talking about. Likewise, a "cvs checkout" without the "-r" option results in this branch. The plans for this branch are not specified; Emacs hackers add to it relatively free of constraint (aside from proper legal / accounting practices), although sometimes there is related discussion on the emacs-devel mailing list. The closure process for this branch is undocumented; concepts such as "freeze", "release", or "integration with the trunk" are not applicable to this branch.