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=K4 IykBi8AfBCJcnSMyIj4IJ9J2coNuvm+ZO/gNaJ6yfWknD2z37XRaDSfIWzvqvxDM orvJg3FPVEcm2UGgkaTkvoMxhGwlaXvQTwBZ3IMjHB92tJQorXBKe6iv4g+fmOXs ZdQ/UK6FDdaUkNuFXAHaTeE3VFdojnf5bnxBy9eUk= 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=nPeaJ+t6 yBULoXQvbHnDO4LCsog=; b=YpNzP0zo5Y6AtyYPrFFdizypQcTFSQpACi7VmFPb 0RI/uzwoz11KEAZgNWghL4w7F48vzej8QufbQRYsF8h/lbZdrS/W0IYnQJ110VVA RAkIMJlu9ZZGs0YPs2CdzmN1xz/oZiSdf/WAHfrr/+U42HlmFVqAhvSr/i55XGH9 Pl0= 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_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-qa0-f42.google.com MIME-Version: 1.0 X-Received: by 10.224.8.9 with SMTP id f9mr1683655qaf.102.1405715742851; Fri, 18 Jul 2014 13:35:42 -0700 (PDT) In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A702E7ECECD@USA7109MB022.na.xerox.net> References: <20140718175905 DOT GA7250 AT ednor DOT casa DOT cgf DOT cx> <0D835E9B9CD07F40A48423F80D3B5A702E7ECECD AT USA7109MB022 DOT na DOT xerox DOT net> Date: Fri, 18 Jul 2014 16:35:42 -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 > 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. Using Gmail, it doesn't seem to offer a way to see them as separate mails or reply to a particular one, though. Oh, well... > 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. Perfect, exactly what I was looking for. Agree it's not the most direct method, but then again solves all the situations I could think of requiring a physical email message that can be replied to. Thanks for the tip Ken! -- 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