Path: ...!3.eu.feeder.erje.net!feeder.erje.net!news2.arglkargh.de!news.karotte.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: VanguardLH <V@nguard.LH>
Newsgroups: news.software.readers
Subject: Re: tin: article stubs one line short
Date: Thu, 19 Sep 2024 23:03:26 -0500
Organization: Usenet Elder
Lines: 39
Sender: V@nguard.LH
Message-ID: <1gzgk2lgv08eo$.dlg@v.nguard.lh>
References: <vchp81$1bo2h$1@paganini.bofh.team>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Trace: individual.net 5/BKooaD9P5S9ovTFm+oMwIlvnLj4nanGRdRe6fmabBYGHZ7c/
Keywords: VanguardLH,VLH
Cancel-Lock: sha1:jOWeHCarQ2EUxyrRYbubdVwNVjg= sha256:agfuNUULhQ5Ima4Q5yLOr38WNy9UgCJfUQZU/d/D2Qc=
User-Agent: 40tude_Dialog/2.0.15.41
Bytes: 2366

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, but you sure the error is
generated by tin, and not by nvi?  You say tin opens the editor, and
then you see the error which makes it appear the editor issues the
error.

Tried getting tin to switch to vim as the editor?