From owner-freebsd-bugs@freebsd.org Tue Oct 18 20:45:18 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5A80AC16B80 for ; Tue, 18 Oct 2016 20:45:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 30858DFA for ; Tue, 18 Oct 2016 20:45:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9IKjGsK068799 for ; Tue, 18 Oct 2016 20:45:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 211360] ESC characters are not interpreted by /bin/sh Date: Tue, 18 Oct 2016 20:45:17 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-BETA1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: jamesekeenan@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2016 20:45:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211360 James E Keenan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jamesekeenan@yahoo.com --- Comment #2 from James E Keenan --- Are there any plans to develop a workaround for this problem for FreeBSD-11= and later? This came up for me -- a relatively new FreeBSD user -- when I went to use = the same assignment to $PS1 in my .shrc on a F11 VM as I had used for several months on a F10.3 VM. The problem was reported to the freebsd-questions mailing list in the thread starting here:=20 https://lists.freebsd.org/pipermail/freebsd-questions/2016-October/274025.h= tml. At first I assumed the problem was due to (a) difference between VirtualBox= and VMware; and/or (b) my own ignorance. But as to (b): I've been setting up colored characters in my command-line prompt on Unix-like OSes since 2001. = And a contributor to that thread indicated he was having the problem in a "bare metal" environment (https://lists.freebsd.org/pipermail/freebsd-questions/2016-October/274041.= html). For reference: uname -a FreeBSD kid51.freebsd11 11.0-RELEASE-p1 FreeBSD 11.0-RELEASE-p1 #0 r306420:= Thu Sep 29 01:43:23 UTC 2016=20=20=20=20 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 I can appreciate that, from one major OS release to the next, there need to= be improvements in basic libraries that can have undesired side effects. But, come on -- people have had color in their prompts for decades. Why give it= up now? This is clearly a regression in user-friendliness. What will it take to develop a workaround? Thank you very much. Jim Keenan --=20 You are receiving this mail because: You are the assignee for the bug.=