Return-Path: <@FINHUTC.HUT.FI:LOJBAN@CUVMB.BITNET>
Received: from FINHUTC.hut.fi by xiron.pc.helsinki.fi  with smtp
	(Linux Smail3.1.28.1 #1) id m0pqlk6-00005SC; Tue, 12 Apr 94 19:55 EET DST
Message-Id: <m0pqlk6-00005SC@xiron.pc.helsinki.fi>
Received: from FINHUTC.HUT.FI by FINHUTC.hut.fi (IBM VM SMTP V2R2)
   with BSMTP id 7745; Tue, 12 Apr 94 19:55:19 EET
Received: from SEARN.SUNET.SE (NJE origin MAILER@SEARN) by FINHUTC.HUT.FI (LMail V1.1d/1.7f) with BSMTP id 7744; Tue, 12 Apr 1994 19:55:20 +0200
Received: from SEARN.SUNET.SE (NJE origin LISTSERV@SEARN) by SEARN.SUNET.SE
 (LMail V1.2a/1.8a) with BSMTP id 2130; Tue, 12 Apr 1994 18:53:53 +0200
Date:         Tue, 12 Apr 1994 16:32:21 +0100
Reply-To:     Colin Fine <C.J.Fine@BRADFORD.AC.UK>
Sender:       Lojban list <LOJBAN%CUVMB.bitnet@FINHUTC.hut.fi>
From:         Colin Fine <C.J.Fine@BRADFORD.AC.UK>
Subject:      Re: Once again...
To:           Veijo Vilva <veion@XIRON.PC.HELSINKI.FI>
Content-Length: 958
Lines: 33

Jorge suggests
++++>
 Maybe you should propose a new cmavo in selmaho ROI, that would be to {roi}
as {moi} is to {mei}. (Unfortunately, the vowels don't help.) Let's call it
{xei},

then:

        mi rexei tcidu          I read a second time
        mi muxei tcidu          I read a fifth time
        mi su'oxei tcidu        I read again
        mi so'ixei tcidu        I read for the umpteenth time
        mi roxei tcidu          I read for the last time

etc.

As with {roi}, these would refer to the second, fifth, whateverth time
in the interval (specified or not).
>++++

I had been thinking that 'krefu' was the best answer, and I still think it's
a good one. But these have a certain attraction. You missed the one
that started it,
        mi su'ipaxei tcidu

But I'm not sure that this merits a cmavo to itself. I think I would express
this by something like

..i su'ipamoi nu mi tcidu

(something is) the +1'th event of my reading.

        Colin