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:from:to:subject:date:message-id:references :in-reply-to:content-type:content-transfer-encoding :mime-version; q=dns; s=default; b=LUDqcCXQ8bZshfYKca+MV0ifxZjTx pDXgXU74tzmD2ugwdUFCmiZqc9A87FPqKOFDFOpXukQI8u0QmM0Eb0qQtEeQjLTm o+jtbWPlavlYde7YX7hqLC/9qSS39f7kcAs0Hd25XD8l3ExB+exafv68rgTEORfl mdSDL1Ch4Ei7W0= 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:from:to:subject:date:message-id:references :in-reply-to:content-type:content-transfer-encoding :mime-version; s=default; bh=ZaVE3rp+84vKM+LcY6EkTYiX0lk=; b=gsT Ywt9W+h3jEq3xhA/IyrcbMux+cT5kM8Ufk06BilzYY/EclB5k+eq/J8E5+zvz1kV d5GhOXHbbQehHP5eWCuF8PTlNDHQ8l2V+xVm5un06GWipcZv+RQsWhsCr2/En2ED bF8WAXbrYe+sT8RpiORBZaq6TMHaWrMbt8EROqYs= 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.2 required=5.0 tests=AWL,BAYES_50 autolearn=ham version=3.3.2 X-HELO: USA7109MR003.ACS-INC.COM From: "Nellis, Kenneth" To: "cygwin AT cygwin DOT com" Subject: RE: Some programs (vi, ssh) crash when screen buffer height is big Date: Fri, 18 Jul 2014 18:48:29 +0000 Message-ID: <0D835E9B9CD07F40A48423F80D3B5A702E7ECECD@USA7109MB022.na.xerox.net> References: <20140718175905 DOT GA7250 AT ednor DOT casa DOT cgf DOT cx> In-Reply-To: <20140718175905.GA7250@ednor.casa.cgf.cx> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id s6IImoPo027149 > From: Christopher Faylor > 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. FWIW, I get digest format, but still make threaded replies (such as this) with a few extra steps that may not be obvious. This presumes using Outlook. YMMV. If you can wait for the digest, you can simply open the selected message from the digest and reply to that, and it will be threaded. If you can't wait, then read the message using your browser and click on the "Raw text" link near the top. The first line will say something like From cygwin-return-191383-listarch-cygwin=... Note the message number 191383. Then you send an empty message to cygwin-get DOT 191383 AT cygwin DOT com and it will mail you back the specified message. You can then reply to it and your reply will be threaded. --Ken Nellis -- 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