faerot

> Its not exposed to API anyhow for now, but can consider it. So please tell what you want to achieve to understand how its better to implement I would...

I assume ```cpp std::string GetAsFile(HANDLE con_hnd, bool colored, bool append_screen_lines = true); ``` Is what would be helpful if exposed to plugin.

> A much better solution is to make WinPort.h functions available to Python, just like C/C++ plugins have. > > switch to user screen: self.parent.info.Control(self.hplugin, self.ffic.FCTL_GETUSERSCREEN, 0, 0) > >...

> unfortunately not :(, the rest is hidden in the _memories buffer then exposing GetAsFile is better

> Wouldn't it be easier to use a decorator to catch errors? Not sure I understood you. Are you questioning the need/usefulness of the plugin which will scan traceback from...

Getting traceback in code as you develop and scanning the crash that already happened and dumped in output are two completely different cases. Scanning traceback from output and opening in...

Looks fine at glance, I will try to play with it a bit later today.

Either it is not working or I don't understand how to use it. I assume ``VTEnumBackground(NULL, 0)`` should return number of con handles available, but it returns 0

Passing actual arguments also does nothing: ```python handles = self.ffi.new('HANDLE[]', 3) total = self.info.FSF.VTEnumBackground(handles, 3) # returns 0 and handles are not changed ```

Ok, figured out VTEnumBackground, works when put some tasks into the background, now VTLogExport not sure if working. This call returns False: ```python fn = b'/tmp/test-log' self.info.FSF.VTLogExport(self.ffi.NULL, 0, self.ffi.new('char[]', fn))...