Date: Sun, 28 Jun 2015 11:59:35 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 201167] units(1) corrupts terminal when run via $() Message-ID: <bug-201167-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201167 Bug ID: 201167 Summary: units(1) corrupts terminal when run via $() Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: jmmv@FreeBSD.org Consider this from today's current: ----- $ units -t ft in 12 $ echo "$(units -t ft in)" 12 $ ----- When running 'units' from within $(), the terminal becomes unusable; note the staircas effect after the second invocation. Carriage returns do not work any longer, nor do control characters such as Ctrl+D. "reset" fixes the carriage return issue, but not everything: for example, backspace cannot work any longer. I have tried this from both the "physical console" (in VMware), a remote session from OS X's Terminal.app, and from within tmux from such remote session. (Do not try on the physical console; getty gets confused once you log out.) I somehow doubt this is a units(1) issue and suspect the problem is coming from libedit, but I'm filing this as a units(1) issue because that's how the problem can be reproduced. (As a related issue, "units -t" should not need to initialize libedit at all -- but it's doing it. Removing that code path "hides" the problem.) -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-201167-8>