X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.6 required=5.0	tests=AWL,BAYES_00,URIBL_RED
X-Spam-Check-By: sourceware.org
Message-ID: <4D40EC49.1080202@bopp.net>
Date: Wed, 26 Jan 2011 21:53:45 -0600
From: Jeremy Bopp <jeremy AT bopp DOT net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: vim wraps lines
References: <op DOT vpxdjthh0gup8g AT daniel-pc> <4D40E281 DOT 7070700 AT cygwin DOT com> <20110127032015 DOT GS5008 AT mrvideo DOT vidiot DOT com>
In-Reply-To: <20110127032015.GS5008@mrvideo.vidiot.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
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

On 01/26/2011 09:20 PM, Mike Brown wrote:
> On Wed, Jan 26, 2011 at 10:12:01PM -0500, Larry Hall (Cygwin) wrote:
>> On 1/26/2011 12:00 PM, Daniel Ajoy wrote:
>>> I'm using the latest cygwin, min-tty and vim
>>>
>>> But when I open vim, lines seem to wrap. Here is the image:
>>>
>>> http://i.imgur.com/oC8lo.png
>>>
>>> Is that a configuration issue? how do I fix it?
> 
> IMHO it isn't broken.  That is the expected behavior.  That is how I use it
> and I want to see all of the line, even if it wraps.
> 
> Why don't you want to see all of the line?

Mike, please take another, closer look at the linked image.  It's clear
that what is displayed is the initial text outputted by vim when started
without a file to open and that the display of this text obviously
broken.  While the problem could have been worded differently to avoid
the confusion, the image makes the problem unambiguous.

It's most likely a problem with the TERM setting in use when vim was
started, as Larry asked to clarify.  I think it's also possible that a
non-Cygwin version of vim was actually started under a Cygwin session.
Larry's suggestion to follow the problem reporting guidelines would
likely clarify this point as well.

BTW, if you didn't intend to comment on Larry's reply at all, you should
have replied to Daniel's message instead.

-Jeremy

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