Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Message-Id: <5.1.0.14.2.20010704072236.0242b638@pop3.cris.com>
X-Sender: rrschulz@pop3.cris.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 04 Jul 2001 07:24:26 -0700
To: "David A. Cobb" <superbiskit@home.com>,
        Sandeep Tamhankar <sandman@Interwoven.com>, cygwin@cygwin.com
From: Randall R Schulz <rrschulz@cris.com>
Subject: Re: Trouble in RXVT with line wrap
In-Reply-To: <5.1.0.14.0.20010704101732.02dfba70@mail>
References: <5.1.0.14.2.20010703174151.0279f238@pop3.cris.com>
 <3B425069.6040200@Interwoven.com>
 <5.1.0.14.0.20010703173051.030d7a90@mail>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

David,

Isn't _what_ a bug? I have no trouble with line wrap, including backspacing 
from a wrapped line back to the line on which typing began. With or without 
readline expansions having been applied.

I experience no troubles whatsoever, and have not since I got the prompt 
strings worked out to properly use \[ ... \].

Randall


At 07:19 2001-07-04, David A. Cobb wrote:
>At 7/3/01 08:47 PM (Tuesday), Randall R Schulz wrote:
>>Hi,
>>
>>Here's a little more on the promt business. It has proved popular with
>>fellow nerds in my office:
>>
>>My PS1 for any terminal (emulator) that supports it (xterm, xterm-color,
>>vt100, vt102, vt220, cytwin, at least) is this:
>>
>>
>>PS1=$'\[\e]0; \u :: \W (\w)\a\]\!> '
>># Note:
>>#  This sequence:
>>#  ESC]0;
>>#      ^ zero
>>#  Starts the title setting sequence. Everything from there to
>>#  the CTRL-G (also "\a" within $'...') is put in the window title.
>>#  Some terminal emulators (notably TeraTerm) put a pretty stingy
>>#  limit on how much they'll display, but you don't have to limit
>>#  the length you attempt to put there
>
>Yes!  Works as advertised and it's a thing of beauty.
>
>But isn't it still a bug in bash (or bash's in-built subset of readline)?
>
>
>>I don't mind the information typically put into prompts, but I _hate_ to
>>have it literally in the prompt!
>>
>>Randall
>
>David A. Cobb


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

