From nobody Sat Dec 16 01:53:58 2023 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SsTf159Gbz54Ndk for ; Sat, 16 Dec 2023 01:54:01 +0000 (UTC) (envelope-from vogelke@pobox.com) Received: from pb-smtp2.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (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 4SsTf10PQxz4TVs for ; Sat, 16 Dec 2023 01:54:01 +0000 (UTC) (envelope-from vogelke@pobox.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=pobox.com header.s=sasl header.b=EpZGW4WU; spf=pass (mx1.freebsd.org: domain of vogelke@pobox.com designates 64.147.108.71 as permitted sender) smtp.mailfrom=vogelke@pobox.com; dmarc=pass (policy=none) header.from=pobox.com Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 240431C0C06; Fri, 15 Dec 2023 20:54:00 -0500 (EST) (envelope-from vogelke@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=date:from :to:subject:message-id:reply-to:references:mime-version :content-type:in-reply-to; s=sasl; bh=lhLIlAGVHpC+gTAmLZydXxrV7R sB2DE6qsP6XHxYy6Q=; b=EpZGW4WUvc+AzaF4rL6+yFSgZb5HYc2ZIwVVFqTA3S BTPcVudoST0ohYLJ1Uj6LX/AaGIOFeINDmxrIkUWwK60xoh+tXPTxi5+o1PoXj7r S8OoI6blIyaZzcgNumjTDOBrJVQ/Iva+3PM+irFamenYN8AbhbhmrPlwgNbVTKxc A= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 18EA61C0C05; Fri, 15 Dec 2023 20:54:00 -0500 (EST) (envelope-from vogelke@pobox.com) Received: from localhost (unknown [98.29.137.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 83E871C0C04; Fri, 15 Dec 2023 20:53:59 -0500 (EST) (envelope-from vogelke@pobox.com) Date: Fri, 15 Dec 2023 20:53:58 -0500 From: Karl Vogel To: freebsd-questions@FreeBSD.org Subject: Re: Problem using vi in freebsd-update from 13.2 to 14.0 Message-ID: Reply-To: vogelke@pobox.com References: <20231215152053.74cf9bf1@opendev.home> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20231215152053.74cf9bf1@opendev.home> X-PGP-Fingerprint: B9B0 D8CF 0413 515D BED4 B507 C123 B01E C8AE 08E9 X-PGP-URL: X-Pobox-Relay-ID: FAE2839E-9BB5-11EE-9CCF-25B3960A682E-01134313!pb-smtp2.pobox.com X-Spamd-Result: default: False [-5.10 / 15.00]; DWL_DNSWL_LOW(-1.00)[pobox.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[pobox.com,none]; R_SPF_ALLOW(-0.20)[+ip4:64.147.108.0/24]; R_DKIM_ALLOW(-0.20)[pobox.com:s=sasl]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.108.71:from]; MLMMJ_DEST(0.00)[freebsd-questions@FreeBSD.org]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[pobox.com:+]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:19151, ipnet:64.147.108.0/24, country:US]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; HAS_REPLYTO(0.00)[vogelke@pobox.com] X-Rspamd-Queue-Id: 4SsTf10PQxz4TVs X-Spamd-Bar: ----- On Fri, Dec 15, 2023 at 10:21:11AM -0500, Roger Marsh wrote: > When doing the merges presented by freebsd-update I have somehow got into > 'ex input mode' and hitting repeatedly does not get me back to > command mode. That drives me nuts. > So, how do I get out of 'ex input mode' in my case? Or can I just kill > the session running freebsd-update and restart freebsd-update assuming > it will pick from where it had got to? Something's hosed your terminal so that pressing escape doesn't send the actual escape character (octal 33). Two things I'd try: 1. Press Control-V Control-Left-Bracket ([) which should send the correct character and let you escape. 2. If that doesn't work, can you fire up a separate ssh session and kill just the running VI? Your terminal will really be hosed now, so when you get back to your prompt, type "stty sane". I'm not sure what interrupting or restarting freebsd-update will do. -- Karl Vogel I don't speak for anyone but myself Keep your booger hook off the bang button. --Firearms safety instructor on Reddit, 30 Nov 2023