https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211360
James E Keenan <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from James E Keenan <[email protected]> --- 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: https://lists.freebsd.org/pipermail/freebsd-questions/2016-October/274025.html. 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 [email protected]:/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 -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
