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=UTLqj9LL4mq22vYSq3j1L19vTf4CC
	XlA2POR15iM638veE0NSW0FJhcnRcDhdzLc1Mlm48rwdAAmrtNe01rsjn1JVauEK
	nKbjggRi5mnqXZkELj6C+pcQF4mUxwmfydhLTVevfiYfBgH+EZGSiUE97R7KXQ2i
	zdkyiPaJbbP/BU=
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=mBDoVTq3PKBIWTjF2s/sad95J2o=; b=g+E
	iQO8q/syrI8RDAlmvWcs00RaUlrtD5yT4e5lCqS2SPmxitweevMetWzU2W8EjlIT
	MohaGwslsakwetj453PWCJlaiA8g8mo2sIVhetMJCCbyIZrd1cCxgyoxvhAbPSDp
	Nar87SM8scih2orUg9BRC0Xi7CVngGjSr6ki8ugg=
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=-0.2 required=5.0 tests=AWL,BAYES_00,MIME_BASE64_BLANKS autolearn=ham version=3.3.2
X-HELO: usa7109mr007.acs-inc.com
From: "Nellis, Kenneth" <Kenneth DOT Nellis AT xerox DOT com>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: RE: Some programs (vi, ssh) crash when screen buffer height is big
Date: Mon, 21 Jul 2014 12:32:34 +0000
Message-ID: <0D835E9B9CD07F40A48423F80D3B5A702E7F0FAD@USA7109MB022.na.xerox.net>
References: <CAHV8iDEPNf-ZFvdVBVw=KhrV5ZopObRhgd7iemDgx9wuWSXWdQ AT mail DOT gmail DOT com>
In-Reply-To: <CAHV8iDEPNf-ZFvdVBVw=KhrV5ZopObRhgd7iemDgx9wuWSXWdQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id s6LCWqui005407

> From: sous lesquels
> <snip> 
> > 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!

Glad to help.
I'm thinking it should be dirt simple for the web site maintainer
to add a hyperlink right on the message web page, perhaps under the
"Raw text" link, which would say something like "Request this message".
It would simply be a mailto: link with the correct message number added.
I'm thinking this could make life much easier for digest readers,
like myself. In the example above, the link would be:
<a href="mailto:cygwin-get DOT 191383 AT cygwin DOT com">Request this message</a>
The only trick would be inserting the proper message number.

--Ken Nellis