X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Tue, 21 Apr 2009 14:15:38 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: DOS programs under "screen" Message-ID: <20090421181538.GE14721@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <416096c60904211046k11a9df2cs95de21653e3ed7df@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <416096c60904211046k11a9df2cs95de21653e3ed7df@mail.gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Tue, Apr 21, 2009 at 06:46:05PM +0100, Andy Koppe wrote: >Andrew Schulman wrote: >>Maybe someone knows a solution to this, but I don't. ?Although I >>maintain screen for Cygwin, I know almost nothing of the details of how >>terminals work. ?I could imagine some kind of a DOS-to-Unix terminal >>wrapper program, but I've never seen one and have no idea how it would >>work. > >It probably can't be done as long as Microsoft doesn't provide a >"pseudo-console" interface that would allow a third-party program to >fully take over the role of a console window. In the meantime, the >best that can be done is the lipstick-on-a-pig approach taken by >http://sourceforge.net/projects/console/, which uses Win32 interfaces >for accessing a console's screen contents and paints its own version of >that. It can be done using the same technique as Console2: http://console.sourceforge.net So there is some justification in invoking the "too lazy" clause. I've started down the path of implementing ptys using console functions a couple of times and have always turned back due to the amount of work it would end up taking. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/