X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4A43B6C6.7040709@aim.com> References: <4A43B6C6 DOT 7040709 AT aim DOT com> Date: Thu, 25 Jun 2009 20:25:09 +0100 Message-ID: <416096c60906251225n304f9eecy9a3cdac91b4d06d5@mail.gmail.com> Subject: Re: Problem with mintty-0.4.1-1 and orpie From: Andy Koppe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 2009/6/25 Mark Harig: > > (TERM=3Dxterm by default for me. I have no idea where that comes from.) > > This is documented in the manual page for 'mintty': > >> TERM variable >> The TERM variable for the child process is set to "xterm", so that pro= =E2=80=90 >> grams that pay attention to it expect xterm keycodes and output xterm=E2= =80=90 >> compatible control sequences. > > There is no documented way in mintty to change the TERM environment before > the shell is started. There's a bit in the TIPS section of the manual on how to set any environment variable using the shell's -c option, e.g.: mintty sh -c "TERM=3Dxterm-256color emacs" > It may turn out to be necessary (some day?) for mintty to > provide some method for the shell to know whether it is running in a mint= ty > terminal or an xterm terminal. There is, but it hasn't made it into the terminal yet. From the 0.4.0 release announcement: - MinTTY now has its own identity, instead of pretending to be an old xterm. The ^E answerback string is "mintty", the ^[[c primary device attribute command reports a vt100, and the ^[[>c secondary DA command reports terminal type 77 (ASCII 'M') and version 400. The TERM variable remains set to "xterm" though, to avoid termcap/terminfo trouble Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple