On Thu, Oct 03, 2019 at 11:56:26AM -0400, sven falempin wrote:
> Dear reader,
>
> If you look an option, the options section does not tell you how to set it
> ( nor where )
> at least this creates a searchable ref between the set ( which you cannot
> find looking for set
> because of the [t] ).
>
hi.
it's probably not explicit since it's fairly straightforward, and
there's an example near page top.
still, your point is a fair one. but there's no "OPTIONS" section - just
"SET OPTIONS", and that doesn;t fit into the text. i wonder if it
wouldn;t make sense to rearrange the text at the start of SET OPTIONS.
SET OPTIONS
There are a large number of options that may be set (or unset)
to change the editor's behaviour.
we could change that to sth like:
SET OPTIONS
There are a large number of options that can change the editor's
behaviour, using the set command.
would that address your issue?
jmc
> Index: docs/USD.doc/vi.man/vi.1
> ===================================================================
> RCS file: /cvs/src/usr.bin/vi/docs/USD.doc/vi.man/vi.1,v
> retrieving revision 1.76
> diff -u -p -r1.76 vi.1
> --- docs/USD.doc/vi.man/vi.1 21 May 2019 09:24:58 -0000 1.76
> +++ docs/USD.doc/vi.man/vi.1 3 Oct 2019 15:52:42 -0000
> @@ -2089,7 +2089,9 @@ in a line, not just the first.
> .Op option? ...
> .Op Ar all
> .Xc
> -Display or set editor options.
> +Display or set editor
> +.Sx OPTIONS
> +.
> .Pp
> .It Cm sh Ns Op Cm ell
> Run a shell program.
>
> - - -
> BTW, on modern system RAM is plentiful while SSD are not always '/tmp'
> friendly.
> 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 .
> Your call of course.
>
> Best.
