From: Thomas S. <th...@ws...> - 2009-03-28 01:48:36
|
So, at least in the past, many console programs would only work correctly inside a cmd.exe windows displayed in a gui session. While others work fine from the msys console, cygwin console, spawned from cygwin ssh, gnu screen for cygwin, etc. Additionally a large subset of those (perhapses all) work in both console "styles". My question is, does anyone know of some notes, the secrete knowledge, or what ever that makes these distinctions? Obviously using memory mapped buffer / DOS style and termcap style operations will yield their logical consequences, but I'm talking about just plain stdio and friends. I'm not even going to mention the word unicode - well at least not in my head. |
From: Greg C. <gch...@sb...> - 2009-03-28 03:29:02
|
On 2009-03-28 01:53Z, Thomas Stover wrote: > So, at least in the past, many console programs would only work > correctly inside a cmd.exe windows displayed in a gui session. While > others work fine from the msys console, cygwin console, spawned from > cygwin ssh, gnu screen for cygwin, etc. Additionally a large subset of > those (perhapses all) work in both console "styles". My question is, > does anyone know of some notes, the secrete knowledge, or what ever that > makes these distinctions? Obviously using memory mapped buffer / DOS > style and termcap style operations will yield their logical > consequences, but I'm talking about just plain stdio and friends. I'm > not even going to mention the word unicode - well at least not in my head. Here's an example of a search that turns up a few messages that may help: http://search.gmane.org/?query=rxvt+buffered&group=gmane.comp.gnu.mingw.msys ...which probably leads to better keywords (e.g., "PTY") for a more refined search. For stdio etc., I flush every stream explicitly when exiting a program. |