Received: from VMS.DC.LSOFT.COM (vms.dc.lsoft.com [205.186.43.2]) by locke.ccil.org (8.6.9/8.6.10) with ESMTP id EAA13340 for ; Sun, 12 Nov 1995 04:02:16 -0500 Message-Id: <199511120902.EAA13340@locke.ccil.org> Received: from PEACH.EASE.LSOFT.COM (205.186.43.4) by VMS.DC.LSOFT.COM (LSMTP for OpenVMS v1.0a) with SMTP id D8CEBBE4 ; Sun, 12 Nov 1995 4:57:35 -0400 Date: Sun, 12 Nov 1995 03:56:28 -0500 Reply-To: cowan@ccil.org Sender: Lojban list From: John Cowan Subject: Re: xruti X-To: jorge@PHYAST.PITT.EDU X-cc: lojban@cuvmb.cc.columbia.edu To: John Cowan In-Reply-To: <199408141958.AA08374@nfs1.digex.net> from "Jorge Llambias" at Aug 14, 94 03:59:58 pm Status: OR X-From-Space-Date: Sun Nov 12 04:02:18 1995 X-From-Space-Address: LOJBAN%CUVMB.BITNET@UBVM.CC.BUFFALO.EDU la xorxes. pupupupu cusku di'e > A plea to remove another place: the x1 of xruti. > > > xruti xru x1 (agent) returns x2 to origin/earlier state x3 from x4; > > The agentive return would be easily formed: xrugau > > Currently, one has to use se'ixru for the agentless x1 returns to state x2, > but that's not really agentless, rather the agent is the one being returned. > So {le bitmu se'ixru le nu blabi} doesn't really mean "the wall is white > again", but rather "the wall made itself white again", or something like > that. > > I think it makes sense to make it agentless. I checked in the text that > I have available, and {xruti} was mostly used in the lujvo {xrukla}, which > even makes more sense with an agentless xruti, and a couple of times it was > used (incorrectly, I suppose) as agentless. Also there were a few {se'ixru}. > I couldn't find any direct use of {xruti} with it's supposed meaning. I was out to lunch when Jorge posted this last year; lojbab asked me to consider it. I approve it and think it should be done ASAP, along with my proposed change for "ckaji". -- John Cowan cowan@ccil.org e'osai ko sarji la lojban.