From LOJBAN@CUVMB.BITNET  Sat Mar  6 22:45:28 2010
Reply-To: Jorge Llambias <jorge@PHYAST.PITT.EDU>
Sender: Lojban list <LOJBAN@CUVMB.BITNET>
Date: Sat Dec  9 18:12:43 1995
From: Jorge Llambias <jorge@PHYAST.PITT.EDU>
Subject:      Re: comments on CONN.TXT
To:         lojban@cuvmb.cc.columbia.edu, jorge@minerva.phyast.pitt.edu
Status: OR
X-From-Space-Date: Sat Dec  9 18:12:43 1995
X-From-Space-Address: LOJBAN%CUVMB.BITNET@UBVM.CC.BUFFALO.EDU
Message-ID: <2Pu4VQpbw1N.A.FEF.Iu0kLB@chain.digitalkingdom.org>

And:
> >  In other words, "act so as to
> > make it true that X happens" does not need {do} to be an argument of X
> > in general.
> Is there no UI that'll do this?

Yes, {ei} (obligation) is the closest to a command. Then there are {e'o}
(suggestion) and {e'u} (request) for other uses of the imperative.
And also there are others for less common uses.

> I imagine that {ko} was influenced
> partly by English imperatives and partly by the wish to make imperatives
> that contain references to the addressee one cmavo shorter.

Yes, I'm not saying that {ko} is not useful. Many commands contain {do}
in the agent place, so {ko} may be a good shortening device. I'm just
commenting that it is not the general way of doing imperatives.

Jorge