Hi Phil, > I never saw this come up on the mailing list - did it get blocked by > something?
Your december mail did not reach the mailing list somehow... The mailing list configuration seems ok. Sourceforge did not report any downtime at that moment. But this last one made it :-) > I get the split gvim screen with pdb in the top and example.py in > the bottom and the => marker on the first line of the program. > > I type :Cmapkeys > the pdb console prints out the key mappings. > > I type <ctrl>-n > > The => marker goes away and nothing more happens. The program > seems dead - no output was produced in the original terminal or in > gvim. I can start again by retyping the :Pyclewn pdb example.py, > but the same thing happens again. Any idea what I am doing wrong? Thanks for the report. I can reproduce the problem. The 'next' command is broken when issued in the bottom frame (the frame that executes the main module), but not elsewhere. I will fix it shortly. Obviously it also lacks a message stating that the program to debug has terminated. -- Xavier Les Chemins de Lokoti: http://lokoti.alwaysdata.net ------------------------------------------------------------------------------ Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
