Path: ...!2.eu.feeder.erje.net!feeder.erje.net!newsfeed.bofh.team!paganini.bofh.team!not-for-mail
From: Anton Shepelev <anton.txt@gmail.moc>
Newsgroups: news.software.readers
Subject: Re: tin: article stubs one line short
Date: Fri, 20 Sep 2024 16:23:46 -0000 (UTC)
Organization: To protect and to server
Sender: 9dIQLXBM7WM9KzA+yjdR4A
Message-ID: <vck7ih$1kifu$1@paganini.bofh.team>
References: <vchp81$1bo2h$1@paganini.bofh.team> <1gzgk2lgv08eo$.dlg@v.nguard.lh>
Injection-Date: Fri, 20 Sep 2024 16:23:46 -0000 (UTC)
Injection-Info: paganini.bofh.team; logging-data="1722878"; posting-host="sFdwXIC/gCdDTLCbP5NXcw.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: 3746
Lines: 69

VanguardLH <V@nguard.lh> wrote:
> Anton Shepelev <anton.txt@gmail.moc> wrote:
> 
>> When I post a new message in Tin 2.6.3, after I enter the subject
>> and press Enter, Tin generates the "stub" of a new article and opens
>> it in my editor (nvi) with `+7', which complains:
>> 
>>    -c option, 1: illegal address: only 6 lines in the file
>> 
>> And indeed, there are only six lines in the generated file:
>> 
>> --------------------------------- Cut ----------------------------------
>> From: Anton Shepelev <anton.txt@gmail.moc>
>> Subject: Russian encodings KOI8-RU and KOI8-R
>> Newsgroups: misc.test
>> Summary: 
>> Keywords: 
>> 
>> --------------------------------- Cut ----------------------------------
>> 
>> whereas I think there should be seven, because one empty line
>> separates the headers from the body, and one begins the body.  It
>> is rather unlikely that the error should be in Tin, but perhaps
>> something is wrong in my environment preventing the second empty
>> line in the generated stubs?
>> 
>> I used the following primitive wrapper script to log the process:
>> 
>> --------------------------------- Cut ----------------------------------
>> echo $* >> ~/invoke.txt
>> cp $2 ~/art.txt
>> vi $*
>> --------------------------------- Cut ----------------------------------
> 
> Haven't been a *NIX user for decades,

Well, both `tin' and `vim' are available on Windows and Mac OS X.

> but you sure the error is generated by tin, and not by nvi?  

I wrote that the error message quoted above is from `nvi', but it
indicates that `tin' may be invokig it incorrectly /or/ generating
an incorrect stub for the article.

> You say tin opens the editor, and then you see the error which makes
> it appear the editor issues the error.

It does, and I have reproduced the error by calling

  >nvi +7 6l.txt

where 6l.txt is a file with six lines.

> Tried getting tin to switch to vim as the editor?

The classic `vi' is the standard editor on my system, but I have
installed vim and tested with it, and there is no error message.
`tin', however, inokes the configured editor with +7 even though
the pre-generated file has only six lines.  Both the editors move
the cursor to the last (sixsth) line of the file, but `nvi'
additionally issues an error message, whereas `vim' stays quiet.
I think `nvi' is correct here, because it is asked to position the
cursor on the senventh line in a six-line file.

It is not a bug in the editor, because regarless of the editor `tin'
2.6.3 on FreeBSD 14.1 pre-generates an article with /only one/ empty
line at the end instead of two.  `tin' 2.6.2 (on a remote system I
use) pre-genenerates articles with two empty lines at the end. I
think it is an error in `tin' 2.6.3.  Or can this have been changed
intentionally?