Date: Wed, 19 Jul 2017 21:13:29 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Dmitry Marakasov <amdmi3@amdmi3.ru> Cc: sjg@FreeBSD.org, rum1cro@yandex.ru, ian@FreeBSD.org, kib@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: [bmake] bmake sigint handling causing tty corruption Message-ID: <6926.1500498809@critter.freebsd.dk> In-Reply-To: <20170718205700.GA2131@hades.panopticon> References: <20170718205700.GA2131@hades.panopticon>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- In message <20170718205700.GA2131@hades.panopticon>, Dmitry Marakasov writes: >In short, when FreeBSD ports options dialog is interrupted by Ctrl+C, >there's chance of sporadic terminal corruption. They are not always >reproducible and seem to be dependent on a machine, shell, terminal, >tmux used, but are not tied to any specific configuration. I've noticed another quirk which may be related: Start vi(1) on some file. Type !some_command_producing_significant_output | less Ctrl-C This leaves the less(1) alive and competing vi(1) for the terminal in a most unworkable and annoying fashion. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6926.1500498809>