Fabien Meghazi <[email protected]> writes: >>> > Sure, you can stick that breakpoint into >>> > $HOME/.config/pudb/saved-breakpoints, in this format: >>> >>> Hey ! that's so cool, using this tip I can even add a key binding in >>> vim in order to generate the breakpoint from the file I'm editing ! >> >> Cool. If you create a vim script that does that, please make a note of >> it here: >> >> http://wiki.tiker.net/PuDB > > Hi Andreas, > > Remember this little chat about a vim plugin that would set/unset breakpoints > ? > A colleague of mine just did it : > > https://github.com/KangOl/vim-pudb > > Now we have to find a way to make pudb watch this file in order to > reload the breakpoint list. > Do you have an idea if this is possible ?
I was half-way done coding this when I noticed that I don't like the semantics of 'watching the file' at all. Suppose you've got two pudb sessions running simultaneously. One exits, and writes the 'saved-breakpoints' file. Should the other one just throw away all the breakpoints it knows about and use the ones from the instance that just exited? Not really. For the moment, I've made an undocumented 'Ctrl-r' shortcut in git that reloads the file. HTH, Andreas _______________________________________________ Pudb mailing list [email protected] http://lists.tiker.net/listinfo/pudb
