Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 16 Dec 2023 12:58:30 +0000
From:      Roger Marsh <roger.marsh@btinternet.com>
To:        freebsd-questions@FreeBSD.org
Subject:   Re: Problem using vi in freebsd-update from 13.2 to 14.0
Message-ID:  <20231216125830.4f91c9f9@opendev.home>
In-Reply-To: <ZX0DNqmXoYUDgL4F@furbag.my.domain>
References:  <20231215152053.74cf9bf1@opendev.home> <ZX0DNqmXoYUDgL4F@furbag.my.domain>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 15 Dec 2023 20:53:58 -0500
Karl Vogel <vogelke@pobox.com> wrote:

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

This did not work for me.

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

Killing vi caused the freebsd-update session to start another vi on the file being edited.  Typing "stty sane" in the separate ssh session was not necessary for me and I did not do it: anyway I got all the edits done and got started on the "Does this look reasonable" prompts for the merges.

> 
>   I'm not sure what interrupting or restarting freebsd-update will do.
> 

I thought I had made a mistake on one of the edits and answered 'n' to the prompt, expecting to be given a vi session to do the edit again.

Instead the freebsd-update job was terminated and I had to restart it anyway.

All went well: just about to install the downloaded upgrades by running "/usr/sbin/freebsd-update install".

I will probably post another question about what happened after answering 'n' to the "Does this look reasonable" prompt.

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

Thanks,

Roger



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20231216125830.4f91c9f9>