Received: from mail-pb0-f59.google.com ([209.85.160.59]:40781)
	by stodi.digitalkingdom.org with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76)
	(envelope-from <bpfk-list+bncBCW7JPVOKYIK54HQRYCRUBGTBPCP4@googlegroups.com>)
	id 1Uwae5-0004TS-FW; Tue, 09 Jul 2013 09:20:14 -0700
Received: by mail-pb0-f59.google.com with SMTP id rq2sf1779901pbb.14
        for <multiple recipients>; Tue, 09 Jul 2013 09:19:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=20120806;
        h=x-beenthere:date:from:to:subject:message-id:mail-followup-to
         :mime-version:user-agent:x-original-sender
         :x-original-authentication-results:reply-to:precedence:mailing-list
         :list-id:x-google-group-id:list-post:list-help:list-archive:sender
         :list-subscribe:list-unsubscribe:content-type:content-disposition;
        bh=dEkrc87jI9e+oR69ssfjzDHLvlat1V/8xD6eWJ6CFls=;
        b=LAVCu+J4fAuiQteyjS2ifHDLMXzClwrO5LRrzG7hVnOrQFpPvEFS9CqfTeaxOIJK8V
         PedmfM0drxJzclE2njn75Y+Q5VJ0tVc3Wq5lNxST4zA5yCv6567ZpuE64DPL3kxNFKjH
         c/7Lw/lA+6cufn6+KPNuAS84aytrGLuClYkagJjK2U8OFPd1jDu033xko+BqScKyDuhq
         nJO4GC/QjtZ5h1wcD4wiCTk2bssHisS6FclBQRdMLrJVSUklmYNqlKItPTnplBODxRKt
         uEh2KGhNhLpiYG+4x5woFxfS9W9nekSnaUEPu8CAGER7BYfBio5lsosab3PlaAToKazT
         N/4A==
X-Received: by 10.50.79.193 with SMTP id l1mr661821igx.14.1373386798890;
        Tue, 09 Jul 2013 09:19:58 -0700 (PDT)
X-BeenThere: bpfk-list@googlegroups.com
Received: by 10.50.130.68 with SMTP id oc4ls2515135igb.42.gmail; Tue, 09 Jul
 2013 09:19:58 -0700 (PDT)
X-Received: by 10.66.102.98 with SMTP id fn2mr588452pab.34.1373386798694;
        Tue, 09 Jul 2013 09:19:58 -0700 (PDT)
Received: from stodi.digitalkingdom.org (mail.digitalkingdom.org. [173.13.139.236])
        by gmr-mx.google.com with ESMTPS id sr2si3105531pbc.2.2013.07.09.09.19.58
        for <bpfk-list@googlegroups.com>
        (version=TLSv1 cipher=RC4-SHA bits=128/128);
        Tue, 09 Jul 2013 09:19:58 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of rlpowell@digitalkingdom.org designates 173.13.139.236 as permitted sender) client-ip=173.13.139.236;
Received: from rlpowell by stodi.digitalkingdom.org with local (Exim 4.76)
	(envelope-from <rlpowell@digitalkingdom.org>)
	id 1Uwadx-0004TN-Ls
	for bpfk-list@googlegroups.com; Tue, 09 Jul 2013 09:19:57 -0700
Date: Tue, 9 Jul 2013 09:19:57 -0700
From: Robin Lee Powell <rlpowell@digitalkingdom.org>
To: bpfk-list@googlegroups.com
Subject: [bpfk] Fiat Attempt #2
Message-ID: <20130709161957.GA16990@stodi.digitalkingdom.org>
Mail-Followup-To: bpfk-list@googlegroups.com
MIME-Version: 1.0
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Original-Sender: rlpowell@digitalkingdom.org
X-Original-Authentication-Results: gmr-mx.google.com;       spf=pass
 (google.com: best guess record for domain of rlpowell@digitalkingdom.org
 designates 173.13.139.236 as permitted sender) smtp.mail=rlpowell@digitalkingdom.org
Reply-To: bpfk-list@googlegroups.com
Precedence: list
Mailing-list: list bpfk-list@googlegroups.com; contact bpfk-list+owners@googlegroups.com
List-ID: <bpfk-list.googlegroups.com>
X-Google-Group-Id: 972099695765
List-Post: <http://groups.google.com/group/bpfk-list/post>, <mailto:bpfk-list@googlegroups.com>
List-Help: <http://groups.google.com/support/>, <mailto:bpfk-list+help@googlegroups.com>
List-Archive: <http://groups.google.com/group/bpfk-list>
Sender: bpfk-list@googlegroups.com
List-Subscribe: <http://groups.google.com/group/bpfk-list/subscribe>, <mailto:bpfk-list+subscribe@googlegroups.com>
List-Unsubscribe: <http://groups.google.com/group/bpfk-list/subscribe>, <mailto:googlegroups-manage+972099695765+unsubscribe@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Spam_score: 0.0
X-Spam_score_int: 0
X-Spam_bar: /


I would like to define the defaults for {za'u} and {me'i} to be
"contextually specified, usually the current value for the thing
under discussion", rather than {pa}.

Two reasons:

1.  {za'u} and {su'o} mean almost exactly the same thing as
currently defined, similarily {me'i} and {su'e}.  Freaking annoying.

2.  Everybody uses them that way anyways; see {za'u re'u}, which is
very common, and has almost no meaning without this change:
http://corpus.lojban.org/corpus/search/za'ure'u?showall=y and
http://corpus.lojban.org/corpus/search/za'u%20re'u?showall=y

In addition, it would give me a clean way to say "I need more flour
for this cake", or whatever.

-Robin

-- 
http://intelligence.org/ :  Our last, best hope for a fantastic future.
.i ko na cpedu lo nu stidi vau loi jbopre .i danfu lu na go'i li'u .e
lu go'i li'u .i ji'a go'i lu na'e go'i li'u .e lu go'i na'i li'u .e
lu no'e go'i li'u .e lu to'e go'i li'u .e lu lo mamta be do cu sofybakni li'u

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