X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS,TBC
X-Spam-Check-By:	sourceware.org
Message-ID:	<COL102-W55257937816B47FC387AE8B5EC0@phx.gbl>
From:	Karl M <karlm30 AT hotmail DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Cygwin 1.7 ssh and window size
Date:	Sun, 6 Sep 2009 16:54:18 -0700
In-Reply-To:	<20090906234041.GC21356@ednor.casa.cgf.cx>
References:	<COL102-W316176F3DDACC50EE94F7DB5F30 AT phx DOT gbl> <COL102-W35F1C8D6AA2D5D87D323D4B5F20 AT phx DOT gbl> <20090831040857 DOT GA2667 AT ednor DOT casa DOT cgf DOT cx> <COL102-W5769CACE9552E85E3C2B58B5F20 AT phx DOT gbl> <h7fnnt$5jl$1 AT ger DOT gmane DOT org> <COL102-W103E97FFD3771B4F7B3050B5F20 AT phx DOT gbl> <20090904141401 DOT GB14283 AT ednor DOT casa DOT cgf DOT cx> <COL102-W16EE786807A25DBC3C5517B5EC0 AT phx DOT gbl> <20090906234041 DOT GC21356 AT ednor DOT casa DOT cgf DOT cx>
MIME-Version:	1.0
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

> Date: Sun, 6 Sep 2009 19:40:41 -0400
> From: cgf
> Subject: Re: Cygwin 1.7 ssh and window size
>
> On Sun, Sep 06, 2009 at 01:18:16PM -0700, Karl M wrote:
>>
>>> Date: Fri, 4 Sep 2009 10:14:01 -0400
>>> From: cgf
>>> Subject: Re: Cygwin 1.7 ssh and window size
>>>
>>> On Sun, Aug 30, 2009 at 11:05:58PM -0700, Karl M wrote:
>>>>My first email had a cygcheck and the following steps to reproduce the
>>>>symptoms.
>>>>
>>>>I just noticed the following with Cygwin 1.7, and ssh (and vi in this
>>>>example), on Vista Business SP2.
>>>>
>>>>If I (1) open a bash cygwin window from the normal installed shortcut
>>>>(cmd.exe).
>>>>
>>>>(2) drag the bottom edge of the window down to enlarge it.
>>>>
>>>>(3) ssh localhost (or to another host).
>>>>
>>>>(4) edit a file with vi.
>>>>
>>>>Then only a portion of the window is used, the size of the original
>>>>window before enlarging it.
>>>>
>>>>If I (5) exit vi, and exit the ssh session.
>>>>
>>>>(6) ssh localhost (or to another host).
>>>>
>>>>(7) edit a file with vi.
>>>>
>>>>Then the entire window is used for editing.
>>>
>>> As I mentioned in another thread, Cygwin's handling of console window
>>> size changes is not perfect. It is hampered by what Windows provides.
>>> I don't see any difference between Cygwin 1.5 and Cygwin 1.7 in this
>>> regard and I would not have expected any since there were no changes
>>> in that part of the code.
>>>
>>With the latest snapshot, if I enter a blank line before ssh localhost,
>>ssh uses the correct window size on the remote host (in this case, the
>>same host), although vi uses the correct window size without a blank
>>line after resizing. So ssh is doing something different than vi in
>>how it deals with window size.
>
> Cygwin's handling of console window size changes is not perfect. It is
> hampered by what Windows provides.
>
I understand that windows causes problems here, but if vi gets the correct
window size and ssh gets the correct window size with Cygwin 1.5 then this
still looks like a regression from Cygwin 1.5 to 1.7.
=20
Thanks,
=20
...Karl
_________________________________________________________________
With Windows Live, you can organize, edit, and share your photos.
http://www.windowslive.com/Desktop/PhotoGallery

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