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:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=Mp Rwn7LYBQsK9adnTYQALMCbO6L6JU3PdUKpuzS8ViARif3fHvW1VcWvcZQIoUl+UV qjAh6I1lf9+FnGRtv2jcDh/Uvgm5tZMt+IwdbUZY9lvQ6mE9lH6v2S0cGdl3Jg1l Che7WOrNuulYnJLrjEyuX9tmweRkwbpnLvTRAOHfk= 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:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=nRrKt2hH t5d31xDgjrzhHxmZY+A=; b=xfs1pFvJBCxnrgPVrcPTgHgJwIrk6TimD+RJVPUn deYT/Xi2vZWG5eq97dbRXU4RDx4eNth+UrO6QUN8GUNR4GVkHTfLkwnNs3ObvYWA g04J32iQC6wJobhiPtH+ySMiwZa+lKgTqXksFucJJ74QRM9d9pdrdWBrxoQF9kKl 1lY= 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.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-qg0-f45.google.com MIME-Version: 1.0 X-Received: by 10.224.161.129 with SMTP id r1mr9342513qax.86.1405702750845; Fri, 18 Jul 2014 09:59:10 -0700 (PDT) In-Reply-To: <53C9427A.4030104@cygwin.com> References: <53C9427A DOT 4030104 AT cygwin DOT com> Date: Fri, 18 Jul 2014 12:59:10 -0400 Message-ID: Subject: Re: Some programs (vi, ssh) crash when screen buffer height is big From: sous lesquels To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Thanks Larry. > This is not the recommended way of handling this situation. You end up > with a ".new" extension if the DLL was in use at the time of your upgrade. > In this case, setup*.exe schedules a replace of your existing DLL with the > ".new" version on reboot. So if you find such a file on your system, the > sanctioned resolution to this is to reboot. OK, thanks for clarifying the update process. I thought maybe setup when started will try to update a file anyway (if not in use at that time, even though it was in use before). Note that I did not know there was "a situation" in the first place :) I definitively rebooted multiple times in between and it looks like it did not get replaced - maybe an issue with scheduling a replace? > You must have subscribed to the list and requested a digest. That I was. > By default, any email replies to this list go to the list. Makes sense, however it would not go to this thread, probably just create a new thread, correct? > The best way to get individual messages from this list that are easy > to reply to is to subscribe without using the digest option Agree, had I been subscribed, I would have gotten the message to reply to, but I unfortunately was only getting digests. Just to note - I'm not asking for the poster to reply to me, just wondering if it's possible to somehow send a mail and tell the mailing list software to thread beneath a specific node of the thread index. E.g. put In-Repy-To: (which I can get from the raw text of the post) in the body or something like that that I'm not aware of? If not, there's no way to thread properly in various cases such as: - I've posted something a month ago and don't want to be spammed by unrelated posts (which would be hundreds in that time span), then a reply comes - I've accidentally deleted the mail - I want to respond to a post that was posted before I subscribed Any suggestions? Or is this not as common use case as I think it is? -- 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