Received-SPF: pass (google.com: domain of seladwa@gmx.de designates 212.227.17.22 as permitted sender) client-ip=212.227.17.22;
Message-ID: <517EB3A7.7000102@gmx.de>
Date: Mon, 29 Apr 2013 19:53:43 +0200
From: selpa'i <seladwa@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: lojban@googlegroups.com
Subject: Re: [lojban] Re: Baby Words: "you're right" and orders.
References: <20130429163424.GP10220@stodi.digitalkingdom.org> <71a0be7f-85af-4b53-8212-8e2de124cf9c@googlegroups.com> <CALm==BUnPBCgz_NZmdZLEnp_T+5tfvULN=x097sJ0pVYSavd5w@mail.gmail.com> <CAHiXx=Pu0Dfk+=ZPMeQCf6M63uPuB0L+0tF-YJ+bw1O08nKddw@mail.gmail.com>
In-Reply-To: <CAHiXx=Pu0Dfk+=ZPMeQCf6M63uPuB0L+0tF-YJ+bw1O08nKddw@mail.gmail.com>
Reply-To: lojban@googlegroups.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
Sender: lojban@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Spam_score: 0.0
X-Spam_score_int: 0
X-Spam_bar: /

la .stevon. cu cusku di'e
> What's the difference between using {e'i} and using {ko}? When would you
> use {e'i} without {ko}, and vice versa?

{ko} is a vague imperative, it can be used for requests and commands 
alike, it can be polite or not.

{.e'i} (under the proposed definition) is explicitly a command, much 
like {.e'o} is explicitly a request.

mu'o mi'e la selpa'i

-- 
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.