I compiled ttyfier successfuly, but it unfortunately didn't solve my
problem. Running Python under tfy causes it to print the normal Python
prompt, then it just hangs and won't respond to any input.
I figured I would email you just in case you had some idea about what
might be going wrong.
I can guess that you're logging in to your cygwin machine from the unix
host, right?
If this is the case, then you're (almost, see below) out of luck.
Ttyfier uses special feature of cygwin console, called "raw-mode input".
tfy.exe sends special command to console application, which makes
console pass each your keypress, encoded, to tfy.exe. It then parses it
and send to the application it's running.
If you ssh from xterm on unix machine to cygwin host, run tfy.exe, then
your xterm continues sending "cooked" keypresses, instead of "raw" ones,
and tfy ignores them.
So to be able to use tfy.exe, your console application must be
'ttyfier-compatible', that is, it must support raw mode of input, which
tfy.exe can understand. If you've been compiling latest sources of
ttyfier, you may have noticed file x11_trans.c inside. This is
experimental module to parse raw input from specially patched xterm (I'm
attaching my old patch to xterm sources).
So, to run your python application from unix machine via ssh you have 2
options:
1. Run cygwin version of python.
2. a. Apply attached patch to xterm sources, and compile special version
of xterm.
b. Build tfy using wide-character version of libncurses
(libncursesw), so that tfy can correctly display pseudo-graphic
characters in unicode xterm window.
Which one is easier, is up to you. I must admit that since i've moved
from windows to linux several years ago, i have not much motivation to
push raw-mode patches to xterm or rxvt.
egor.