X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Andrew DeFaria Subject: Re: terminal escape codes Date: Mon, 08 May 2006 19:10:55 -0700 Lines: 23 Message-ID: References: <445B9333.6090109@cygwin.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) In-Reply-To: X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk 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 Igor Peshansky wrote: > On Fri, 5 May 2006, Andrew DeFaria wrote: >> Jeff Lange wrote: >>> While that does work, It unfortunately isn't an acceptable solution >>> for me. I really need to be running this from a plain text console. >> How is running rxvt not a plain text console?!? I use rxvt all the >> time. I don't like the "Windows window" as it's cut and paste >> semantics are horrible as well as it's resizing (in)ability. > Windows has a notion of a "console window". rxvt, xterm, ssh, and > pretty much any other Cygwin program that doesn't allocate an explicit > console window uses ptys to emulate console output. Some Windows > programs cannot understand ptys, and thus don't work properly via ssh, > or in rxvt. So the OP's need may be valid. I'm well aware of this and indeed this is about the only drawback I've ever seen with using rxvt instead of the console window. But there are not that many "Windows only, I need a console and I can't deal with pty's" applications that I run. Indeed many Windows users shy away from anything command line oriented. My question was more to affirm whether or not the OP was running into a pty problem or just didn't understand that he could use rxvt... -- If olive oil comes from olives, where does baby oil come from? -- 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/