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:message-id:date:from:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=wjHIOOc0swb8X2Zb
	cgSR8MGC0IBAnVV3MiR650DhmXFom5+L41Xmd4Rttlf1HqC+xEV8DJyI/h16E0dJ
	slpEt6q6eQJwAZ1xqzRBvKTm/vw++TdCDfZ95NJlFZpidEAbT2WXW+nfQtsWZpL+
	V3W31JKDZVaNBjxFrYEN2PjEWd0=
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:message-id:date:from:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=HIr29I9FQSYNa7Nc4kwysy
	ZsX5Y=; b=vIJLfmyORCemOrDfXeqc9/wmXqmoFaMxhilEOp0Ys5HKuUfiqbp36J
	oL+yhpWH554BjaT5vkclE1NDBlkKGPtRuUQ3zFGtFPLz4NtJsN2c6zQrl5poNPTQ
	BAnaGMC+AaPvaJNi96FJr7QOWSSvrMxvqZHqB65DJtZQIi4uDOqLM=
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.4 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-Spam-User:	qpsmtpd, 2 recipients
X-HELO:	Ishtar.hs.tlinx.org
Message-ID:	<550B5840.3020600@tlinx.org>
Date:	Thu, 19 Mar 2015 16:14:08 -0700
From:	Linda Walsh <cygwin AT tlinx DOT org>
User-Agent:	Thunderbird
MIME-Version:	1.0
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
CC:	cygwin-xfree AT cygwin DOT com
Subject:	Re: Disable xterm auto-wrap: Mess up vi-like command line
References:	<loom DOT 20150224T155835-41 AT post DOT gmane DOT org>
In-Reply-To:	<loom.20150224T155835-41@post.gmane.org>
X-IsSubscribed:	yes

Paul wrote:
> If I disable auto-wrap, the vi editing at the comand line misbehaves
> when the line being edited is long, especially when yanking a lot of
> text and pasting it.  I suppose that this might be technically correct
> behaviour, since an extra long command line needs to wrap in order to
> see it properly.  But I use the vi command line exclusively, and
> almost always, I don't want autowrap in the results from commands
> being sent to the screen.  Is there a way to get both at the same
> time, without having to always toggle the xterm autowrap?
---
What do you mean by "mess up"?  It "shouldn't".  I just cut and pasted some text
from an xterm into an editor, and the lines weren't split... they got copied as
one line.

However, if I was to cut from a Windows Console window (cmd.exe for example),
it DOES, physically, split long lines.

It's a property of the console.

The main problem I've seen in bash is when you paste content that has
tabs in it.  Then bash tries to auto complete in the middle of your 
typing... often asking a question or pausing -- which means it *swallows* 
up the tab and 1-2 keys after the tab.

It didn't use to do this back in the 3.x series, but was added as a new
feature in the 4.x series.  

I ended up changing my "completion character" to BACKQUOTE to try to get
around this. 

Maybe tabs are causing your problem?

Example.  At a prompt, I typed:
cat "<CR>
<completion char>

(I hit enter after that first quote and went to the next line and hit
my completion char (BACKQUOTE "`"), Then I got:
> cat "
> 
Display all 186 possibilities? (y or n)
---
At this point, whatever character is next in my paste buffer will be
swallowed up (in addition to the completion character).

---

Since the long line cut/paste worked for me in 'xterm', that's why I
thought maybe you were hitting bash'es "input mangling"-feature!...




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