it talks to it through pipes rather than with a real pty, and the issues there are deep and woolly. Turns out the problem is how cygwin interfaces a non-cygwin console app from the terminal. but i needed mouse action on the desktop and screen (which uses a text-based x windows server) remotely. the mysterious thing was it would work from a non-x cygwin shell. neither the interpreter nor the debugger prompt would show up, and nothing happened when i used print or. cape - cyclically adjusted price/earningsįinally solved a problem (or found a workaround, at least) for something that had bothered me for a while: when i tried to use windows python (not cygwin python, which worked fine) in a xterm, it seemed not to be connected to stdout, stderr, and stdin.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |