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=mX
	kATp/FoVmfJlJxKzKAIu1GWqdUiDt8WtXeIg0QVmZzQxMgfVm3JTSg2pyIIWLs03
	ijyg94aUbDnhQNjAurhkFfIvN/+2T4HC1GMBsnR5+vXfZXptQ+kJWCgs2goX4nlA
	ViuTEglDuKpjChtjVIeq58d/vFiW5dZ5JU3z6QlIs=
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=/cD1C5gK
	71hFUKMnu3cDj7qOTfU=; b=HOfyMAzp83Ij8EG1wpPP+Nozoprm93+CXmviN2Br
	I0PWY4r+l/R5JSQD75nE5g2MJESirD5AW1HbPPqdNl14Z+l6NNZyJOzg4pIQ08ky
	OiAnTyBcnCNyoL7lcxv+5LytnPfQQtRPCf+jujqH21VvN9iK3PrQbTIxngD355tQ
	g9Y=
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_05,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-oi0-f48.google.com
MIME-Version:	1.0
X-Received:	by 10.202.102.146 with SMTP id m18mr5468732oik.112.1440768214672; Fri, 28 Aug 2015 06:23:34 -0700 (PDT)
In-Reply-To:	<55DFB10C.3050804@cygwin.com>
References:	<CAHV8iDH4pG0FoGrckc36atQUV+SWOnryJ-zBDK92HTGgPRC=Ew AT mail DOT gmail DOT com> <26A19798-1F20-4D52-A311-C8312E0D4621 AT etr-usa DOT com> <CAHV8iDGU8tN+58LR10e3zHxiEsr5ekXrKrLeyYRAD0tx0H6B1A AT mail DOT gmail DOT com> <6DC9320F-4DCC-47E4-AB8C-3158EBD6260E AT etr-usa DOT com> <CAHV8iDFauqCe-aKZB6Ba1oJbOvvOr7M19ZyJJVu-t8DQ46f=ug AT mail DOT gmail DOT com> <CAN=he+XN0qiLjm+K+0Qr13=GqtvAyJSArdFh873++1=dTjP35Q AT mail DOT gmail DOT com> <CAHV8iDH=FL3XQ0OrK0pzLPOP+7-VK88HvD2_k2zzWZTc+hyXdw AT mail DOT gmail DOT com> <55DC9C55 DOT 9090404 AT gmail DOT com> <CAHV8iDEw1fp4-yXLd1sjKMvKvCzemuEFNbUy4FJ-zvxWQZC26g AT mail DOT gmail DOT com> <55DFB10C DOT 3050804 AT cygwin DOT com>
Date:	Fri, 28 Aug 2015 09:23:34 -0400
Message-ID:	<CAHV8iDGw3FWOBBdNQ0HcBCpwAHRQrpTj6YbNjE8o4AnCe77zqA@mail.gmail.com>
Subject:	Re: Some programs (vi, ssh) crash when screen buffer height is big
From:	Sous Lesquels <a9f54d2 AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes

Thanks Larry.

> I think you're misunderstanding where the limitation is coming from.

I don't think I'm misunderstanding anything - I was actually thinking
along the same lines that you just wrote.

I feel that with increasing monitors sizes == increasing window sizes,
it might happen more often, as not all people use mintty. I can change
from ConEmu to mintty, but IMHO that's like saying I can use the
stairs instead of an elevator in Burj Khalifa. I don't and cannot
expect anything from Cygwin team, which is providing something I like
and use every day. If there are more important problems that mine
never comes to the top, then that's what it is.

I still hope someone will be able to check. It looks to me this might
be one of those "640k will be enough" problems, with some buffer with
fixed size that nobody anticipated will not be "big enough". Or it
might be something completely different. Even if it's just me that's
affected, I understandably would like that to stop happening. If it
does, I'd be so much happier. If it doesn't, tough luck. I've been
dealing with several dozen restarts each day for at least a year when
I first reported the problem, but I still like it and use it.

Saying "it's ms bug", "it's a design choice", "it's a bug, but we
don't have time / resources to fix it", "it happens so rarely, we
don't care", "it's going to be fixed in 2030", etc. is fine with me.
It might mean that I should not expect this to work any time soon or
ever, but it would be a honest answer and, if coming from someone on
the team itself, hopefully correct. Instead, a few different people
replied to me on this thread with "you misunderstanding, ignorant
quack".

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

- Raw text -