On Thu, Jul 8, 2010 at 10:49 AM, HarKoT wrote:
> Hi Xavier,
> I'm using pyclewn 1.2
> The Operating system of the machine is Red Hat Enterprise Linux Server
> release 5.4 (Tikanga)
> and I'm starting vim in a screen session inside Putty.
> The second thing I've tried is running gvim from Exceed on demand 6.
> Each time I'm starting Pyclewn from inside vim by typing :Pyclewn.
> Thanks for your help
> tony
When using vim, the debuggee output is redirected to '/dev/null'. So
in this case you must tell gdb to redirect the debuggee output to
another console.
Start two putty sessions:
* on the first one run xterm and inside xterm run the command
'tty' to get the name of the terminal. Assume for example that
the command output is:
'/dev/pts/2'
* on the second session, run vim, start pyclewn and gdb, and run
the command:
':Cset inferior-tty /dev/pts/2'
now all debuggee output goes to the first xterm console
I don't now Exceed, but maybe a simpler solution would be to run xterm
from Exceed, and then from this xterm, start gvim (not vim). The
debuggee output would go to the xterm console.
Xavier
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Pyclewn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyclewn-general
