Re: Minor vi MAN helper/precisions
On Fri, Oct 04, 2019 at 12:35:40PM +0100, Stuart Henderson wrote: > On 2019/10/04 07:22, sven falempin wrote: > > On Fri, Oct 4, 2019 at 4:29 AM Stuart Henderson > > 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, 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.121 May 2019 09:24:58 - 1.76 > > +++ vi.13 Oct 2019 17:01:14 - > > @@ -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.. > hmm. i have to admit, i agree with stuart. i overlooked the ugliness because it seemed neat to have a handy link, but i do think it reads worse. > > @@ -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. > so i will probably commit just this chunk. jmc > > This section describes the options, their abbreviations and their > > default values. > > .Pp > > >
Re: Minor vi MAN helper/precisions
On 2019/10/04 07:22, sven falempin wrote: > On Fri, Oct 4, 2019 at 4:29 AM Stuart Henderson 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, 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 - 1.76 > +++ vi.1 3 Oct 2019 17:01:14 - > @@ -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 >
Re: Minor vi MAN helper/precisions
On Fri, Oct 4, 2019 at 4:29 AM Stuart Henderson 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, 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 ? -- -- - Knowing is not enough; we must apply. Willing is not enough; we must do
Re: Minor vi MAN helper/precisions
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, 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
Re: Minor vi MAN helper/precisions
On Thu, Oct 03, 2019 at 12:43:20PM -0400, sven falempin wrote: > On Thu, Oct 3, 2019 at 12:15 PM Jason McIntyre wrote: > > > > 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 > > > > Ok, SET OPTIONS is written as `.Sh SET OPTIONS` , > and yes > I did not understand that SET was the command, > not why the sections was named like that . > At first I just enter option=value in the .exrc file '-_- > > Nevertheless this is still less easy as you cannot search '/set' in > the man because of the se[t] > and the fact that set is very common word. > Looking for OPTIONS ( not options ) should reveal the link between the two > IMHO. > > -Display or set editor options. > + Display or > + .Sx SET OPTIONS > + of the editor. > i thought of this but, to my knowledge, we've never used an Sx as a kind of inline text. but i suppose it could be this way too. > And your text change really does not hurt . > > Best. > that would leave the diff below. anyone? jmc 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.121 May 2019 09:24:58 - 1.76 +++ vi.13 Oct 2019 17:01:14 - @@ -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. @@ -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. This section describes the options, their abbreviations and their default values. .Pp
Re: Minor vi MAN helper/precisions
On Thu, Oct 3, 2019 at 12:15 PM Jason McIntyre wrote: > > 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 > Ok, SET OPTIONS is written as `.Sh SET OPTIONS` , and yes I did not understand that SET was the command, not why the sections was named like that . At first I just enter option=value in the .exrc file '-_- Nevertheless this is still less easy as you cannot search '/set' in the man because of the se[t] and the fact that set is very common word. Looking for OPTIONS ( not options ) should reveal the link between the two IMHO. -Display or set editor options. + Display or + .Sx SET OPTIONS + of the editor. And your text change really does not hurt . Best.
Re: Minor vi MAN helper/precisions
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.121 May 2019 09:24:58 - 1.76 > +++ docs/USD.doc/vi.man/vi.13 Oct 2019 15:52:42 - > @@ -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, 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.
Minor vi MAN helper/precisions
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] ). 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.121 May 2019 09:24:58 - 1.76 +++ docs/USD.doc/vi.man/vi.13 Oct 2019 15:52:42 - @@ -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, 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.
