bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [50 character or so descriptive subject here (for reference)]


From: Chet Ramey
Subject: Re: [50 character or so descriptive subject here (for reference)]
Date: Thu, 12 Sep 2002 09:28:50 -0400

> Configuration Information [Automatically generated, do not change]:
> Machine: i586
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i586' 
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i586-mandrake-linux-gnu' 
> -DCONF_VENDOR='mandrake' -DSHELL -DHAVE_CONFIG_H  -D_GNU_SOURCE 
> -D_FILE_OFFSET_BITS=64  -I.  -I. -I./include -I./lib -I/usr/include -O3 
> -fomit-frame-pointer -pipe -mcpu=pentiumpro -march=i586 -ffast-math 
> -fno-strength-reduce
> uname output: Linux Multivac.home 2.4.18-6mdk #1 Fri Mar 15 02:59:08 CET 2002 
> i686 unknown
> Machine Type: i586-mandrake-linux-gnu
> 
> Bash Version: 2.05
> Patch Level: 1
> Release Status: release
> 
> Description:
> I put the variable PS1 to "\033[1;34m\u@\h:\w\033[0m\$ " (to have great 
> colors)
> But when typing a long line command (like $ lkjsdf lj sjdlkf  lkjds lkj 
> sdflkj lkjdsflkjs  lkjdsf lksda lkj sdflk lakdjf lkjsdf lksjf), bash begins 
> to bug. Just test it, and you will see what it makes. It's been a long time 
> the issue exists.

Read the Bash FAQ, question E3.  That's been there for a long time, too.

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )

Chet Ramey, ITS, CWRU    chet@po.CWRU.Edu    http://cnswww.cns.cwru.edu/~chet/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]