From owner-freebsd-bugs Sun Jun 25 20:50: 7 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 1DC8037B5CA for ; Sun, 25 Jun 2000 20:50:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id UAA54964; Sun, 25 Jun 2000 20:50:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Sun, 25 Jun 2000 20:50:04 -0700 (PDT) Message-Id: <200006260350.UAA54964@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bernd Luevelsmeyer Subject: Re: misc/19388: bash prompt problem, or perhaps curses problem Reply-To: Bernd Luevelsmeyer 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: Bernd Luevelsmeyer To: FreeBSD-gnats-submit@freebsd.org Cc: Doug Barton Subject: Re: misc/19388: bash prompt problem, or perhaps curses problem Date: Mon, 26 Jun 2000 05:44:37 +0200 Doug Barton wrote: [...] > 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. [...] I was indeed using Bash 2.03. I have now updated to 2.04 and the problem has not changed. The same effect happens on NetBSD 1.4.2 (bash 2.03 there); so, unless they have the same curses-or-whatever bug, it's indeed a bash problem. I will report to bashbug. Thanks, B. Luevelsmeyer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message