Skip to content

Conversation

@mvanderkamp
Copy link

Does so through the use of sign groups.
Also:

  • Provide an UpdatePudbBreakPoints command
  • Provide options for configuring the breakpoint sign

@mvanderkamp
Copy link
Author

Derp sorry I forgot that pushing a bunch more changes to my master branch would land them here as well- I should have done the pull request from a feature branch. I'll be happy to make one if you only want a subset of the changes.

Done by updating breakpoints immediately if in a python file when
sourced
Just because we don't interact with conditions (yet) doesn't mean we
should abolish them
Seems redundant- the whole point of the plugin is to manage breakpoints.
You know what you're in for when you start typing "Pudb..."
Fix some wording in the introductory paragraph.
This fixes an annoying bug where your ability to set breakpoints would
be based entirely on whether or not there was an executable line at the
place you want the breakpoint when you first opened the file for
editing.
mvanderkamp and others added 27 commits April 12, 2021 19:40
If a buffer was not loaded, the line numbers were often being looked up
in some other loaded buffer, usually the current one, giving the wrong
line text in the populated list.

The problem was a redundant call to bufname().
Not sure why I did that...
Instead of the line of code
- Signs update on save
- List commands don't try to figure out the line of code
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant