From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 45733 invoked by alias); 19 Mar 2015 23:14:17 -0000 Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com Received: (qmail 45717 invoked by uid 89); 19 Mar 2015 23:14:17 -0000 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 Received: from ishtar.tlinx.org (HELO Ishtar.hs.tlinx.org) (173.164.175.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 19 Mar 2015 23:14:15 +0000 Received: from [192.168.4.12] (Athenae [192.168.4.12]) by Ishtar.hs.tlinx.org (8.14.7/8.14.4/SuSE Linux 0.8) with ESMTP id t2JNE8Qx090945; Thu, 19 Mar 2015 16:14:12 -0700 Message-ID: <550B5840.3020600@tlinx.org> Date: Tue, 31 Mar 2015 18:36:00 -0000 From: Linda Walsh User-Agent: Thunderbird MIME-Version: 1.0 To: "cygwin@cygwin.com" CC: cygwin-xfree@cygwin.com Subject: Re: Disable xterm auto-wrap: Mess up vi-like command line References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-03/txt/msg00014.txt.bz2 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 " (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!... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/