From owner-freebsd-bugs Sun Jun 25 16:30: 5 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id BE6CE37B52B for ; Sun, 25 Jun 2000 16:30:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id QAA28687; Sun, 25 Jun 2000 16:30:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Sun, 25 Jun 2000 16:30:01 -0700 (PDT) Message-Id: <200006252330.QAA28687@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Doug Barton Subject: Re: misc/19388: bash prompt problem, or perhaps curses problem Reply-To: Doug Barton Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/19388; it has been noted by GNATS. From: Doug Barton To: bdluevel@heitec.net Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: misc/19388: bash prompt problem, or perhaps curses problem Date: Sun, 25 Jun 2000 16:22:43 -0700 bdluevel@heitec.net wrote: > If you have escape sequences in a bash prompt, and execute > several long commands (longer than one line) so that they > are in the history buffer, and then press cursor-up and > cursor-down to change between these commands, the prompt > may be messed up and the displayed command lines too. If you are not already, please try Bash 2.04. There were several improvements in ANSI escape sequence handling. If you are having additional problems after upgrading, please use bash-bug to report them. This is a Bash problem, not a FreeBSD one. Good luck, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message