[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Bug in escape sequences on the prompt
From: |
Fei Lung |
Subject: |
Bug in escape sequences on the prompt |
Date: |
Sun, 4 Mar 2001 22:50:48 -0500 (EST) |
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_\
MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DSHELL -DHAVE_CONFIG_H
-D_FILE_OFFSET_BITS=6\
4 -I. -I. -I./include -I./lib -I/usr/local/include -g -O2
uname output: Linux ambesc.homeip.net 2.4.1 #2 Tue Feb 20 02:43:01 EST 2001
i686 unknown
Machine Type: i686-pc-linux-gnu
Bash Version: 2.04
Patch Level: 0
Release Status: release
Description:
When using bash in either console, screen, or an xterm, there is a
problem with using the escape sequences in PS1. If there are any escape
sequences, then commands typed past the end of the line will not continue
on the next. It will overwrite the current line. Tested on bash 1.14,
2.03, 2.04
Repeat-By:
export PS1="^[[36m- ^[[0m" (that's C-v ESC[36m)
Type a lot of characters till it goes past the end of line
Fix:
Haven't looked at the code, but it works if you do
export PS1="\033[36m- \033[0m" (without using the actual escape
character
Fei Lung
$ chown flung universe
- Bug in escape sequences on the prompt,
Fei Lung <=