X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:references:to:from:reply-to:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=q2xr92FP8+bRNhRh 341x56tSY0acAp7yczS2DYIpxgFBQGzkmPD4J5I7WxJWmbklS+6uQhD0O94J9lbF vayQ7zcY5omkulY+wcflAYPdZkLgXl2iVS5tHRMQvy8Sej+B00lj2cnYMVxSuc5r lCbbli5vt7ip1vt9K8EktzAhwZI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:references:to:from:reply-to:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=/v1YhvSlj3VRtMgHUrY0xR PI6kE=; b=d00F6QoG65UJcr9qYCrBgEpBgQ9aQRdjCix5B2WOuOZd5belY6sGxz vS10684ghIWodvYeyAUILq7YIJxavbgO3W6vrhucHLnAhXPh83BpjntfeTlQ/DNh qudvF0kLZfQdsSvQxVqmuJslIc2VnzTYiMtRHrRzDTzp9EUOGY2RY= 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.1 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=fonts, movements, H*RU:64.59.134.9, Hx-spam-relays-external:64.59.134.9 X-HELO: smtp-out-no.shaw.ca X-Authority-Analysis: v=2.2 cv=JLBLi4Cb c=1 sm=1 tr=0 a=WqCeCkldcEjBO3QZneQsCg==:117 a=WqCeCkldcEjBO3QZneQsCg==:17 a=IkcTkHD0fZMA:10 a=NEAV23lmAAAA:8 a=HiWkEfo4AAAA:8 a=syrkiINGIp7xpV9bl48A:9 a=QEXdDO2ut3YA:10 a=NGto_iE5OMEA:10 a=Bn2pgwyD2vrAyMmN8A2t:22 a=_QplDg0m8TGAdENQf2wZ:22 Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.7.4 References: <87vasqrl2a DOT fsf AT Rainer DOT invalid> To: cygwin AT cygwin DOT com From: Brian Inglis Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Message-ID: <25e79ef3-c0ca-2d9f-7353-413580222412@SystematicSw.ab.ca> Date: Sun, 5 Feb 2017 13:36:27 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfI9QTC7bf2alyL8F3+cSYKgp6gR+6RXMt0vzaEvy3P9f+kHRJ82f1T0cau3x2QM0AC16l4YrzFLKX18mQqlzyZEbWlfd47CNwcMiOWQHm8vwjfV1uun4 3dkPK1yBVFfdFX5tdFYglnIwRu33NlUiszjYNSve8ICwtalHjxdMXYNvmOzSiP5oYlba+N+rYKLOUQ== X-IsSubscribed: yes On 2017-02-05 11:35, Thomas Wolff wrote: > Hi Achim, > > Am 04.02.2017 um 17:13 schrieb Achim Gratz: >> Thomas Wolff writes: >>> I have uploaded mintty 2.7.4 with the following changes: >> Since about November/December last year I'm having problems with >> screen and tmux sessions in mintty not correctly refreshing and >> leaving garbage characters displayed in the terminal. It seems that >> the terminal size is not always correctly reported, especially if >> you make the window occupy the left or right half of the screen via >> Windows shortcut. > Is this within tmux or after leaving tmux (see comment below)? It > would be help to cross-test this; if it's mintty, which version > would show the behaviour first? What happens in xterm? >> Additionally, there seems to be an off-by-one bug when the last >> line of the terminal needs to be scrolled up in order to show >> content that is longer than the remaining width. This happens when >> you for instance recall a long command from history. It's hard to >> see what exactoly happens, but it looks like the one character too >> many gets printed (and wraps onto the next line) before the whole >> terminal window gest scrolled up and the rest of the command gets >> printed in the line below the single wrapped character. That >> remainder is in various states of disarray, showing both remnants >> from the original prompt on the last line (now three lines up), >> empty /spaces where there should have been characters from the >> command and then of course parts of the command. > This might be related to some issue with terminal geometry as > perceived by the shell (see > https://github.com/mintty/mintty/issues/377#issuecomment-137728631). > Have you checked that? Recently changed your prompt? Try with basic > prompt (PS1="\w> ") please. Thanks for supporting and enhancing mintty to be even better in Cygwin, and able to be used as a console for other environments. The test below may be relevant to the above problem, or may be unrelated. Running vttest 2.7 (20140305) http://invisible-island.net/vttest/vttest.html updated by and used by xterm maintainer for testing. Test 1. Test of cursor movements screens 3 80 col mode and 4 132 col mode gives results looking like below (shortened lines to 71 characters to avoid wrap issues and fixed content to match display results): Test of autowrap, mixing control and print characters. The left/right margins should have letters in order: M m N n O o P p Q q R r S s T t U u V v W w X x Y y Z z Push Unfortunately most of the test documentation is in the source as tables. If you find vttest useful, it might be worth adding to the mintty package as a test program, where you or others could ask users with problems to run specific tests, as xterm does. It may also be useful if mintty had some character hex value box display mode switch to display the actual codes at each visual position, or maybe a font used to display the character hex value in a box, often used in fonts as glyphs for non-printing control characters and those in the Private Use Area, in which case that could perhaps be added to the mintty package for use in testing. I have been searching for such a font with no success so far. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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