X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <496E4AA4.8080904@gmail.com> Date: Wed, 14 Jan 2009 20:27:16 +0000 From: Andy Koppe User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: MinTTY 0.3.4 References: <495917BA DOT 1090401 AT gmail DOT com> <49613928 DOT 503 AT gmail DOT com> <4966897B DOT 2010805 AT gmail DOT com> In-Reply-To: <4966897B.2010805@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Hi, I've uploaded MinTTY 0.3.4 to http://code.google.com/p/mintty. This is a more substantial bugfix release than the previous one, which addresses the following issues: - In 'application cursor mode' the cursor keys sent xterm-incompatible keycodes when combined with a modifier, starting the sequence with ESC O instead of ESC [. This is now fixed, which means e.g. that combinations such as should now work out-of-the box in vim. Nevertheless it's an incompatible change, so apologies to anyone who adapted their scripts to MinTTY's incorrect behaviour. This change also affects the keycodes sent by the mousewheel when on the alternate screen and not in app mouse mode. For the mousewheel to work in less, .lesskey therefore now should look as follows (assuming 'Shift' is the modifier key for scrolling): \e[1;2A back-line \e[1;2B forw-line - There was a crash when scrolling beyond 32K lines. (The scrollback limit is actually set to 64K lines, not 16K as previously mentioned.) - The Linefeed/Newline Mode (LNM) parameter was ignored. - When selecting multiple lines, the first character on the last line was always included. - Signals were not processed immediately. - MinTTY keeps its window open when the command it runs reports failure, so that any error output can be read (which is useful e.g. with ssh). However, this did not deal with signals properly. Now it will stay open only if the command exited with non-zero status or was terminated by a runtime error signal such as SIGSEGV or SIGILL. Andy -- 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/