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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=TAgkxLPNGWNjvcROkn4HJ0Aiz+dspOO0EgS5StCIalQNuRuO54Qvn
	uZ4v/ViJYwHgfedW/IN+3l1SXh9OQIEjz74LPVa4/ndRz2GQ05jO20/seQXY79ku
	0O1rRL/xi9QSP5zC8Y9TUhkvdvubgPvsQHhW3p1JXjXWXOE2CvnjdE=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=lvXPe7aa82b7In3h0GJbzCv9KSo=; b=XQjAtICedRscDF01LpOCDzzf/Gdr
	S3YVpzdB2CeP3ngvu4waey+hFQ3BXZPEMFYE2I7iK5xRO75FI2OaQFV+YnorEG3K
	ZlmJFqf6KGXoJwph4koKv27odA4JJIlmN5ao2a95sic8crt2+X93oe5zZQScwHPy
	2RfmdyaGDedLn34=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: mho-01-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX185a6BIJCCUlc9Q50U5TJUK
Date: Fri, 18 Jul 2014 13:59:05 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Some programs (vi, ssh) crash when screen buffer height is big
Message-ID: <20140718175905.GA7250@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAHV8iDHxzqOwQW6ZTfE1J1AWoJjqSB49cUPrR3M=KrgP19=NPA AT mail DOT gmail DOT com> <CAHV8iDG3JeKK1pF+Upk8+7zvqTRzir7r2Rp6-R_gGwH8cwpTmw AT mail DOT gmail DOT com> <CAHV8iDHFYe__rQ5ghDNgHfj_GJ6ObVDfmx4u9aXRDzURN-C8UQ AT mail DOT gmail DOT com> <53C9427A DOT 4030104 AT cygwin DOT com> <CAHV8iDGsixVTdcB=Bkk2OeRUAVjfy=CotCMUdNdUR6Sxx0Q+eg AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAHV8iDGsixVTdcB=Bkk2OeRUAVjfy=CotCMUdNdUR6Sxx0Q+eg@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Fri, Jul 18, 2014 at 12:59:10PM -0400, sous lesquels wrote:
>Any suggestions? Or is this not as common use case as I think it is?

Craft your reply with the appropriate "In-Reply-To" header tag and it
will maintain threading.

There is no automated way to do that if you are using the digest.  Digests
are intended for casual perusal of the list, not for active communication.

--
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