delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/04/22/19:52:52

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
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.1.0.6.0.20040422194204.0390fa40@127.0.0.1>
X-Sender:
Date: Thu, 22 Apr 2004 19:48:33 -0400
To: Andrew DeFaria <Andrew AT DeFaria DOT com>, cygwin AT cygwin DOT com
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Subject: Re: Line breaks in bash
In-Reply-To: <c69h99$uh2$1@sea.gmane.org>
References: <c69h99$uh2$1 AT sea DOT gmane DOT org>
Mime-Version: 1.0

At 06:34 PM 4/22/2004, you 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?


Works fine for me.


>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, apparently.  I could reproduce your problem using your prompt.


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019