On Sat, Dec 24, 2011 at 6:46 AM, Michael Shavlovsky wrote: > > Hello! > I want to see watched buffer (clewn)_dbgvar My actions: 1. run > Pyclewn from command line. Gvim is automatically opened 2. write in > gvim :open myprog.cpp 3. then :Cfile main. where main compiled > myprog.cpp with g++ and options -ggdb -Wall. 4. set breakpoint and > run the program (:Crun) 5. When program is waiting on break point I > write :Cdbgvar n (n is variable I want to know value). The problem > that whether I got exeption (missing unified_diff control line) or I > see gvim empty buffer "(clewn)_dbgvar". Is this bug or I am doing > something wrong?
This seems to be caused by changes made in the difflib module of the python standard library in python 7.2 (and also probably in python 3.2.2). I will look into it and fix this pyclewn issue 3464903. -- Xavier Les Chemins de Lokoti: http://lokoti.alwaysdata.net ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
