Path: ...!2.eu.feeder.erje.net!feeder.erje.net!newsfeed.bofh.team!paganini.bofh.team!not-for-mail From: Anton Shepelev Newsgroups: news.software.readers Subject: Re: tin: article stubs one line short Date: Sat, 21 Sep 2024 19:39:16 -0000 (UTC) Organization: To protect and to server Sender: 9dIQLXBM7WM9KzA+yjdR4A Message-ID: References: <1gzgk2lgv08eo$.dlg@v.nguard.lh> Injection-Date: Sat, 21 Sep 2024 19:39:16 -0000 (UTC) Injection-Info: paganini.bofh.team; logging-data="2040593"; posting-host="WJi3VZ6YDT03B/ZmmBPfhA.user.paganini.bofh.team"; mail-complaints-to="usenet@bofh.team"; posting-account="9dIQLXBM7WM9KzA+yjdR4A"; User-Agent: tin/2.6.3-20231224 ("Banff") (FreeBSD/14.1-RELEASE (amd64)) X-Notice: Filtered by postfilter v. 0.9.3 Bytes: 1889 Lines: 19 Joerg Mertens wrote: >Anton Shepelev wrote: >> >> I love this noise and am glad to meet a vi user online. Have you >> noticed that its -c option is documented as if accepting the command >> after a space: -c ? This form does not work for me, and I >> have to use it without the inervening space: -c . Is it an >> error in the man page, or I am missing someting? > >It works here with both the system nvi (OpenBSD) and the nvi from ports. >The former is version 1.79 and the ports nvi is 2.2.1. > >For example: > ># vi -c '/^$/' file > >starts on the first blank line of the file, Yes, you are right. I had blundered, by trying -c '+3'.