On Wed, Oct 17, 2012 at 10:59 PM, Wojtek <[email protected]> wrote: > On 17.10.2012 18:57, Xavier de Gaye wrote: >> On Tue, Oct 16, 2012 at 11:42 PM, Wojtek wrote: >>> I have one more question. >>> Could you give me any hint to easiest way to redirect (clewn)_console to >>> outside tty(pts) no to buf in vim. >> >> Do you want to only redirect the console, what about the watched >> variables window ? >> > Yes I was thinking about it - its good for me , but wouldn't be a problem > to expand watched variables? In vim's buffer its make by X (foldvar), > how in tty? > I note it would be best for me to redirect to previous opened pts not to > open > a new one for console.
With the attached patch to the python2 branch, gdb output is redirected to the terminal from which pyclewn has been launched and the (clewn)_console window is not used. The following changes have been made: debugger.py: remove all the lines in the vim script function s:winsplit() netbeans.py: replace calls to ClewnBuffer.append with calls to sys.stdout methods (with python3, one would use instead: print(self.buffer, end='')) tty.py: remove the line that sets the terminal in raw mode I don't plan to include this patch in pyclewn. -- Xavier Les Chemins de Lokoti: http://lokoti.alwaysdata.net
console_redirection.patch
Description: Binary data
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
