X-Recipient: archive-cygwin@delorie.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=RWjon0i/JE0IRAJEBCKVt0T4q8CBWy4OMcAUL8LUFRHHj/0r+jwh9
	7GAd3UxAuLWuAQQhm4H02qCf3K1DHXZk+sMXPkA/SHAyC8LB25+I9udzfA7/pNhn
	WNOK5FrmqfodF3ouKMwVCJv2wbmkh2s8/SM2Zq8rjEHOaX8qTtrGEM=
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=ewIl5R9/TSu06janMhQqOGO7rgA=; b=RYvKCiz+1b0V/3WbZ5U+7B4M9O6h
	L28PwMEZmMewiDbIDj8sFI+x93ZjKtX3v1tKVWoRjmdtDnvtWBuAOKPRoB+ZfG4b
	oSCp/Ko8Q3x0QERlG2hznQNAYTrxouv78vEnMip9tX/nFb0bF0vyUC8J22UEtQ0b
	M0o4xiCFSngZIm8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=AWL,BAYES_40,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: mho-02-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX18OIa9i9r7oG6OxOo1YUckE
Date: Tue, 22 Jul 2014 20:49:58 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Some programs (vi, ssh) crash when screen buffer height is big
Message-ID: <20140723004958.GA723@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <CAHV8iDEPNf-ZFvdVBVw=KhrV5ZopObRhgd7iemDgx9wuWSXWdQ@mail.gmail.com> <0D835E9B9CD07F40A48423F80D3B5A702E7F0FAD@USA7109MB022.na.xerox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A702E7F0FAD@USA7109MB022.na.xerox.net>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Mon, Jul 21, 2014 at 12:32:34PM +0000, Nellis, Kenneth wrote:
>> 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.191383@cygwin.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.191383@cygwin.com">Request this message</a>
>The only trick would be inserting the proper message number.

No, we're not going to change the way the web archive works.  There is
no easy way that the archiving software would know what the mailto: link
would be.  And, I'm not too interested in hacking at the archiver
anyway.

I'll say it again: Just add the In-Reply-To or References with the right
Message-ID and you'll get threading.

cgf

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