delorie.com/archives/browse.cgi | search |
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 |
Message-ID: | <20040423003718.93970.qmail@web21205.mail.yahoo.com> |
Date: | Thu, 22 Apr 2004 17:37:18 -0700 (PDT) |
From: | AJ Reins <tbisp AT yahoo DOT com> |
Subject: | Re: Line breaks in bash |
To: | cygwin AT cygwin DOT com |
In-Reply-To: | <c69h99$uh2$1@sea.gmane.org> |
MIME-Version: | 1.0 |
X-IsSubscribed: | yes |
--- Andrew DeFaria wrote: > When I type a long line in the bash shell it seems to get confused when > it passes the first 80 character barrier and does a newline. Below is an > example. > > C09-272-A:# why is it in bash that when I get close to typing 80 > characters bash > does som > ething like this? > > Now set my prompt to the hostname as > "\[\e]0;\w\a\e[01;33mC09-272-A:\e[0m". Could this be causing the problem? Yes. You have a \[ to indicate non-printing characters without the closing \]. > -- > I don't suffer from insanity. I enjoy every minute of it. Me too! (sorry about that! (acutally I'm not, but lets not quibble over tribbles!)) __________________________________ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |