From araizen@newmail.net Fri Jun 22 04:34:11 2001 Return-Path: X-Sender: araizen@newmail.net X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-7_1_3); 22 Jun 2001 11:34:11 -0000 Received: (qmail 15210 invoked from network); 22 Jun 2001 11:34:11 -0000 Received: from unknown (10.1.10.26) by l10.egroups.com with QMQP; 22 Jun 2001 11:34:11 -0000 Received: from unknown (HELO hp.egroups.com) (10.1.2.220) by mta1 with SMTP; 22 Jun 2001 11:34:11 -0000 X-eGroups-Return: araizen@newmail.net Received: from [10.1.10.124] by hp.egroups.com with NNFMP; 22 Jun 2001 11:34:11 -0000 Date: Fri, 22 Jun 2001 11:34:06 -0000 To: lojban@yahoogroups.com Subject: Re: kona, but not the coffee Message-ID: <9gvafe+v6re@eGroups.com> In-Reply-To: <26.1720ee9b.28637e9d@aol.com> User-Agent: eGroups-EW/0.82 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Length: 969 X-Mailer: eGroups Message Poster X-Originating-IP: 62.0.182.42 From: "Adam Raizen" la pycyn cusku di'e > But 1) {ko} is specific to imperative mode: its primary use is exactly > coextensive with that mode. i ma smuni zoizoi imperative mode zoi i pe'i ca le nu minde cei cusku be zo ko mu'a cu jarco lo selcni > 2) the referent of {ko} defaults to that of {do} but {ko} is > assignable, as we learned in an earlier thread, to any nameable group or > object i li'a do kakne le nu cusku lu doi mi'o ko co'e li'u mu'a i gendra gi'e te jimpe i ku'i tolmle carmi pe'i i melmau fa le nu pilno lo se cinmo valsi i ja'ebo le se cinmo valsi ka'e se pilno kansa la'e zo do ji'a i secaubo nitcu le valsi po'u zo ko > > I'm not sure I follow the rest: how does {ko} fit talking about the topic of > conversation only? i le se tavla ka'e na se casnu i zo ko cu mapti le nu minde la'e zo do to li'a la'e zo do se tavla gi'u te tavla toi enaike la'e zo mi'o e le simsa i za'a do na tugni i ku'i ai mi noroi cusku lu doi mi'o ko li'u mu'o mi'e adam