Received: from mail-vc0-f189.google.com ([209.85.220.189]:61904) by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from ) id 1T2m4A-0004X7-4A; Sat, 18 Aug 2012 09:40:16 -0700 Received: by vcbfl10 with SMTP id fl10sf4779039vcb.16 for ; Sat, 18 Aug 2012 09:39:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:received-spf:mime-version:sender:in-reply-to:references :from:date:message-id:subject:to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe:content-type; bh=gfUewqE0haQFyZbsGTM8/MVU/lKe0SxGq7d2kS8HQKw=; b=7KzhNI+Aw0nwLYJrBEptalchkKuT4x/loJ7NVVJD2Zupwg/wvX9VEHxo8davUtnpF7 EMBL09L14Eaz7+uwawybQm4IFgucQxLL0uDxQUX+Uzi1IcVX6MiSE2EYOgFsxYKwhlXy AJH70AwJfRa0AtV+9KgERnb7uWnh37PpT6X2I= Received: by 10.50.183.195 with SMTP id eo3mr1151633igc.6.1345307994514; Sat, 18 Aug 2012 09:39:54 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.50.11.232 with SMTP id t8ls3286608igb.2.canary; Sat, 18 Aug 2012 09:39:53 -0700 (PDT) Received: by 10.43.105.135 with SMTP id dq7mr3428461icc.3.1345307993906; Sat, 18 Aug 2012 09:39:53 -0700 (PDT) Received: by 10.43.105.135 with SMTP id dq7mr3428460icc.3.1345307993891; Sat, 18 Aug 2012 09:39:53 -0700 (PDT) Received: from mail-ob0-f177.google.com (mail-ob0-f177.google.com [209.85.214.177]) by gmr-mx.google.com with ESMTPS id xd1si2429132igb.1.2012.08.18.09.39.53 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 18 Aug 2012 09:39:53 -0700 (PDT) Received-SPF: pass (google.com: domain of rpglover64@gmail.com designates 209.85.214.177 as permitted sender) client-ip=209.85.214.177; Received: by mail-ob0-f177.google.com with SMTP id ta17so8322392obb.8 for ; Sat, 18 Aug 2012 09:39:53 -0700 (PDT) Received: by 10.60.21.103 with SMTP id u7mr6564879oee.49.1345307993688; Sat, 18 Aug 2012 09:39:53 -0700 (PDT) MIME-Version: 1.0 Sender: lojban@googlegroups.com Received: by 10.76.132.2 with HTTP; Sat, 18 Aug 2012 09:39:33 -0700 (PDT) In-Reply-To: <3c8e9a9a-2f9b-4c00-8052-ebe2605507c8@googlegroups.com> References: <23861931-0238-4ac4-a76e-60a8ea1b4d75@googlegroups.com> <502E37FF.5000500@gmx.de> <3c8e9a9a-2f9b-4c00-8052-ebe2605507c8@googlegroups.com> From: ".arpis." Date: Sat, 18 Aug 2012 12:39:33 -0400 Message-ID: Subject: Re: [lojban] {ko}, {xa'e}, {.e'u}, {e'o} To: lojban@googlegroups.com X-Original-Sender: rpglover64@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of rpglover64@gmail.com designates 209.85.214.177 as permitted sender) smtp.mail=rpglover64@gmail.com; dkim=pass header.i=@gmail.com Reply-To: lojban@googlegroups.com Precedence: list Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com List-ID: X-Google-Group-Id: 1004133512417 List-Post: , List-Help: , List-Archive: List-Subscribe: , List-Unsubscribe: , Content-Type: multipart/alternative; boundary=e89a8ff1c71e13cbec04c78ced97 X-Spam-Score: -0.7 (/) X-Spam_score: -0.7 X-Spam_score_int: -6 X-Spam_bar: / --e89a8ff1c71e13cbec04c78ced97 Content-Type: text/plain; charset=ISO-8859-1 That is absolutely false. {ko} is simply the word for an imperative mood, with no other implications; it's not necessarily an order. On Sat, Aug 18, 2012 at 11:32 AM, la gleki wrote: > {.e'u} and {ko} largely differ in the fact that after insubmission after > {ko} you might be executed by your commander whereas after {.e'u} you would > probably survive. zo'o > > > On Friday, August 17, 2012 4:24:31 PM UTC+4, selpa'i wrote: >> >> Am 17.08.2012 13:47, schrieb Paul Predkiewicz: >> > but {xa'e} is a rafsi of {xance}, how would you use it to say such >> > things as "let's go"? >> >> -xa'e- is the rafsi, but xa'e as a cmavo is a LAhE (even though I wish >> it was UI) that makes it so that the sumti it's used on is treated as if >> it was ko, i.e. a third-person command. >> >> xa'e lo gerku cu cliva >> "The dogs shall leave!" >> "May the dogs leave!" >> "I want the dogs to leave." >> >> Whether it's very useful is another question. {.e'u} will usually be >> enough for cohortatives at least. >> >> mu'o mi'e la selpa'i >> >> -- >> pilno zo le xu .i lo dei bangu cu se cmene zo lojbo .e nai zo lejbo >> >> -- > You received this message because you are subscribed to the Google Groups > "lojban" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/lojban/-/uwcGoYr3b0UJ. > > To post to this group, send email to lojban@googlegroups.com. > To unsubscribe from this group, send email to > lojban+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/lojban?hl=en. > -- mu'o mi'e .arpis. -- You received this message because you are subscribed to the Google Groups "lojban" group. To post to this group, send email to lojban@googlegroups.com. To unsubscribe from this group, send email to lojban+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/lojban?hl=en. --e89a8ff1c71e13cbec04c78ced97 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable That is absolutely false. {ko} is simply the word for an imperative mood, w= ith no other implications; it's not necessarily an order.

On Sat, Aug 18, 2012 at 11:32 AM, la gleki <gleki.is.my.name@gmail.com> wrote:
{.e'u} and {ko} largely differ in the fa= ct that after insubmission after {ko} you might be executed by your command= er whereas after {.e'u} you would probably survive. zo'o


On Friday, August 17, 2012 4:24:31 PM UTC+4, selpa'i wrote:Am 17.08.2012 13:47, schrieb Paul Predk= iewicz:
> but {xa'e} is a rafsi of {xance}, how would you use it to say = such=20
> things as "let's go"?

-xa'e- is the rafsi, but xa'e as a cmavo is a LAhE (even though= I wish=20
it was UI) that makes it so that the sumti it's used on is treated = as if=20
it was ko, i.e. a third-person command.

=A0 =A0 =A0xa'e lo gerku cu cliva
=A0 =A0 =A0"The dogs shall leave!"
=A0 =A0 =A0"May the dogs leave!"
=A0 =A0 =A0"I want the dogs to leave."

Whether it's very useful is another question. {.e'u} will usual= ly be=20
enough for cohortatives at least.

mu'o mi'e la selpa'i

--=20
pilno zo le xu .i lo dei bangu cu se cmene zo lojbo .e nai zo lejbo

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To view this discussion on the web visit https://groups.google.com= /d/msg/lojban/-/uwcGoYr3b0UJ.
=20 To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com.
For more options, visit this group at http://groups.google.com/group/lojba= n?hl=3Den.



--
mu'o mi= 'e .arpis.

--
You received this message because you are subscribed to the Google Groups "= lojban" group.
To post to this group, send email to lojban@googlegroups.com.
To unsubscribe from this group, send email to lojban+unsubscribe@googlegrou= ps.com.
For more options, visit this group at http://groups.google.com/group/lojban= ?hl=3Den.
--e89a8ff1c71e13cbec04c78ced97--