On Tue, Jun 14, 2011 at 6:31 PM, Uri Moszkowicz <[email protected]> wrote: > Are there any plans to create a TTY without opening another terminal (and > then garbage collect it when vim exits)? That's an undesirable burden. As to > the S-X problem, the only error I see in the (clewn_console) is "Not a valid > line number.". I'm trying to like the new Python interface but it's hard to > as the old vimGdb seemed better in several respects, the most notable being > this TTY problem. I'm not thrilled about this "Press enter to continue" > message when netbeans starts. It looks like Pyclewn attempts to hit enter > for you sometimes but it doesn't work all the time. Sometimes Pyclewn takes > a while to start, either in nbstart or waiting for GDB but I'm not sure what > the cause is. Maybe it's just non-deterministic garbage collection from > Python.
vimGdb does not implement a terminal. When using gvim (instead of vim) and launching gvim from a terminal, then pyclewn creates a pseudo tty that uses this terminal and restores this terminal in its initial state on vim exit. So there is no additional burden there. The S-X key maps to the 'foldvar' command which expects a valid line number (see the documentation). In the netbeans interface, the debugger front-end (pyclewn) is the server and the editor (Vim) initiates the connection. The delay you observe from time to time is because Vim succeeds only on the second connection attempt. -- Xavier Les Chemins de Lokoti: http://lokoti.alwaysdata.net ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Pyclewn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyclewn-general
