Hi,
Using the latest pyclewn I have noticed the cursor disappears in the active vim
window after a pyclewn/gdb command (eg. interrupt, break). A cursor movement
key (eg 'j') will cause it to reappear. I'm not sure if this was a problem
before but have only just noticed it.
If the active window was the (clewn)_console prior to the command, the active
window (and later cursor) switches to the other (I generally use two: console
and source). This may however be fixing a previous minor irritation in that an
interrupt with the console window active would load the current source into it
rather than the existing source window: I usually keep the source window active
for this reason.
nb NBDEBUG 1:insert/41 655 "Quit\n[Thread debugging using libthread_db
enabled]\n[New Thread 0x7fffea63c710 (LWP 6905)]\n\nProgram received signal
SIGINT, Interrupt.\n0x00007ffff30afb93 in select () from /lib64/libc.so.6\n"
nb NBDEBUG 1:setDot!42 842
nb NBDEBUG 1:setReadOnly!43 T
nb NBDEBUG 0:endAtomic!44
nb NBDEBUG 41
pyclewn mercurlial latest (3195072), gdb 7.2, vim 7.3 (console)
thanks,
Rob
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
Pyclewn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyclewn-general
