On 2019/10/04 07:22, sven falempin wrote: > On Fri, Oct 4, 2019 at 4:29 AM Stuart Henderson <s...@spacehopper.org> wrote: > > > On 2019/10/03 11:56, sven falempin wrote: > > > BTW, on modern system RAM is plentiful while SSD are not always '/tmp' > > > friendly. > > > > Some of the slower media (CF/SD cards etc) might have issues eventually but > > I would expect anything worthy of the name 'SSD' should be fine. > > > > > Using tmpfs for /tmp, <breaks> vi unless you create a proto with > > vi.recover > > > subdir or create it on rc.local. > > > maybe a mkdir /tmp/vi.recover.uid would make sense, or just a mktemp . > > > > eh? > > > > - vi.recover is created by /usr/libexec/vi.recover which is run from > > /etc/rc already > > > > - tmpfs is disabled in the kernel config for a reason > > > > I will investigate why I lose the directory so often . Meant MFS , no > custom kernel. > Last time it’s just a no reboot situation * > > Are you ok with the man changes ?
> Index: vi.1 > =================================================================== > RCS file: /cvs/src/usr.bin/vi/docs/USD.doc/vi.man/vi.1,v > retrieving revision 1.76 > diff -u -r1.76 vi.1 > --- vi.1 21 May 2019 09:24:58 -0000 1.76 > +++ vi.1 3 Oct 2019 17:01:14 -0000 > @@ -2089,7 +2089,9 @@ > .Op option? ... > .Op Ar all > .Xc > -Display or set editor options. > +Display or > +.Sx SET OPTIONS > +of the editor. > .Pp > .It Cm sh Ns Op Cm ell > Run a shell program. Not really a fan of this, it doesn't read very nicely to me and it's totally obvious already.. > @@ -2273,9 +2275,11 @@ > not in > .Nm ex . > .Sh SET OPTIONS > -There are a large number of options that may be set > -.Pq or unset > -to change the editor's behavior. > +There are a large number of options that can > +change the editor's behavior, > +using the > +.Cm set > +command. I don't mind this, I suppose it might help people who read "SET OPTIONS" without reading 'FAST STARTUP' or the ex commands list. > This section describes the options, their abbreviations and their > default values. > .Pp >