On Fri, Jun 30, 2017 at 09:19:31AM -0600, Anthony J. Bentley wrote:
>
> Here's a diff that updates the STANDARDS section in the manual.
> I think it will be enough to talk about our POSIX compliance. POSIX
> discusses its differences from historical ex/vi in great detail,
> including an explicit
On Fri, Jun 30, 2017 at 09:19:31AM -0600, Anthony J. Bentley wrote:
> Christian Weisgerber writes:
> > On 2017-06-29, "Anthony J. Bentley" wrote:
> >
> > > The vi manual is long enough. It doesn't seem very helpful to keep stubs
> > > that have been stubs for 20 years.
> >
>
Christian Weisgerber writes:
> On 2017-06-29, "Anthony J. Bentley" wrote:
>
> > The vi manual is long enough. It doesn't seem very helpful to keep stubs
> > that have been stubs for 20 years.
>
> Should we retain some documentation along the lines of "nex/nvi
> does not
On 2017-06-29, "Anthony J. Bentley" wrote:
> The vi manual is long enough. It doesn't seem very helpful to keep stubs
> that have been stubs for 20 years.
Should we retain some documentation along the lines of "nex/nvi
does not implement the following options from the
Hi,
>From vi(1):
lisp [off]
(...) This option is not yet implemented.
modelines, modeline [off]
(...) This option will never be implemented.
optimize, opt [on]
(...) This option is not yet implemented
redraw, re [off]