Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Subject: RE: bash & $PS1 (display error)
Date: Sat, 1 Feb 2003 14:18:56 -0500
Message-ID: <83040F98B407E6428FEC18AC720F5D732DB7B2@exchange.tropicnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Rolf Campbell" <rcampbell AT tropicnetworks DOT com>
To: <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h11JJ7h18314

> -----Original Message-----
> From: Randall R Schulz [mailto:rrschulz AT cris DOT com] 
> Sent: Saturday, February 01, 2003 2:01 PM
> To: Rolf Campbell; cygwin AT cygwin DOT com
> Subject: RE: bash & $PS1 (display error)
> 
> 
> Rolf,
> 
> That's hardly surprising. I assumed you encountered the 
> problem because 
> you were working in a deeply nested directory with a very 
> long absolute 
> name. To me, even modest-length directory names are intrusive when 
> included in the shell prompt, which is why I offered my 
> alternative. Do 
> you just want to have an incredibly long prompt?

Well, I began my computer use in DOS, and it was standard to include the
path in the prompt.  And I have no choice but to use deeply nested
directories (large build system makes it difficult to avoid).  The real
problem I was having is in bash, when I use ^R to do a reverse search on
the command history, and then hit enter to run the command, I find that
it frequently has display problems.  When trying to make a simple test
case, I discovered this specific problem.

I have no overwhelming desire to have extremely long prompts, but I
think that they should either be:
#1) Available & working.
#2) Not available.
#3) Available & not working 100%, but the limitation known.

I realize the issues with open-source software.  If I have a problem
that nobody else cares about, I will have to fix it myself.  I just
wanted to see if anyone knew what was going on, or even just to inform
people of the limitation.

I've downloaded the cygwin bash source, but it's going to be a while
before I will be able to figure out how to fix this problem (haven't
even been able to find the part of the code responsible for printing the
prompt yet).

-Rolf

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