Return-Path: LOJBAN%CUVMB.BITNET@vms.dc.LSOFT.COM Received: from SEGATE.SUNET.SE (segate.sunet.se [192.36.125.6]) by xiron.pc.helsinki.fi (8.6.12/8.6.9) with ESMTP id BAA08481 for ; Sat, 9 Dec 1995 01:58:57 +0200 Message-Id: <199512082358.BAA08481@xiron.pc.helsinki.fi> Received: from listmail.sunet.se by SEGATE.SUNET.SE (LSMTP for OpenVMS v1.0a) with SMTP id FBA9A8DD ; Sat, 9 Dec 1995 0:58:57 +0100 Date: Fri, 8 Dec 1995 23:56:15 +0000 Reply-To: ucleaar Sender: Lojban list From: ucleaar Subject: Re: comments on CONN.TXT X-To: lojban@cuvmb.cc.columbia.edu To: Veijo Vilva Content-Length: 862 Lines: 17 Jorge: > > 7. 13.7 "An imperative sentence [lio] is true if the command is obeyed". > > The discussion is potentially misleading. It should be explained that > > one could obey the command not only by bringing tea, but also by instead > > making this not be coffee. Therefore it is only an approximate and > > misleading translation of the English. > I'm glad you think that. The fact that {do} is an argument of the > command is purely circumstantial, that's why I think that an attitudinal > is much better than {ko} for imperatives. 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? 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. --- And