From owner-freebsd-current@freebsd.org  Wed Jul 19 21:19:59 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 55B2DD7EB6E
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Wed, 19 Jul 2017 21:19:59 +0000 (UTC)
 (envelope-from phk@phk.freebsd.dk)
Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222])
 by mx1.freebsd.org (Postfix) with ESMTP id 20AB76D3F2;
 Wed, 19 Jul 2017 21:19:58 +0000 (UTC)
 (envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (unknown [192.168.55.3])
 by phk.freebsd.dk (Postfix) with ESMTP id 58F312738B;
 Wed, 19 Jul 2017 21:13:33 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
 by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id v6JLDTE9006927;
 Wed, 19 Jul 2017 21:13:29 GMT (envelope-from 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
In-reply-to: <20170718205700.GA2131@hades.panopticon>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
References: <20170718205700.GA2131@hades.panopticon>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6925.1500498809.1@critter.freebsd.dk>
Date: Wed, 19 Jul 2017 21:13:29 +0000
Message-ID: <6926.1500498809@critter.freebsd.dk>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 21:19:59 -0000

--------
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.