Received: from mail-wi0-f184.google.com ([209.85.212.184]:33310) by stodi.digitalkingdom.org with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.80.1) (envelope-from ) id 1Ya9rQ-0006pE-Pp for lojban-list-archive@lojban.org; Mon, 23 Mar 2015 14:26:21 -0700 Received: by wiwh11 with SMTP id h11sf13231196wiw.0 for ; Mon, 23 Mar 2015 14:26:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-original-sender:x-original-authentication-results :reply-to:precedence:mailing-list:list-id:list-post:list-help :list-archive:sender:list-subscribe:list-unsubscribe; bh=eTum2AbWBBfKF9yIEYCmtuR0SSx+ep5Xe3EaIupu+1E=; b=tFm8rioYiIPwtIOytD5n5g5mm3gUuVn5UFBrILOQTTM7MYZtYYafuhNhkd8ns7fUn6 HkXRGA0NseYEQHMtTV3Xp1qPgKuTK3iZalNeF3+aTtyAXOncJxM8YTAgOk+QdlFyJiH+ ZkGz0rUbMfBUgiMRj3kIwTRmp90cAjQynQuvHt2E8YcoASC7b+7G6umbj7QwoiMa1ukQ yZSSFR+FNLmHGJkMqsJHcmhnCT0YW96iZX43Mkk1zN7DPmGqN5/UPLmHfMVAgj4pH5bZ jieWJSam1/xOA8PelE+2uUM4faz+c9MxI0j6jIrwWw78XVOQnBMZasEOFsXzMHXxyV3T DqPA== X-Received: by 10.152.7.203 with SMTP id l11mr16032laa.4.1427145966015; Mon, 23 Mar 2015 14:26:06 -0700 (PDT) X-BeenThere: lojban@googlegroups.com Received: by 10.152.25.193 with SMTP id e1ls740048lag.80.gmail; Mon, 23 Mar 2015 14:26:05 -0700 (PDT) X-Received: by 10.112.77.101 with SMTP id r5mr237120lbw.4.1427145965343; Mon, 23 Mar 2015 14:26:05 -0700 (PDT) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com. [2a00:1450:400c:c05::236]) by gmr-mx.google.com with ESMTPS id o3si554211wib.2.2015.03.23.14.26.05 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Mar 2015 14:26:05 -0700 (PDT) Received-SPF: pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::236 as permitted sender) client-ip=2a00:1450:400c:c05::236; Received: by mail-wi0-x236.google.com with SMTP id dy8so58750731wib.0 for ; Mon, 23 Mar 2015 14:26:05 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.94.164 with SMTP id dd4mr2185191wjb.56.1427145965244; Mon, 23 Mar 2015 14:26:05 -0700 (PDT) Received: by 10.27.86.219 with HTTP; Mon, 23 Mar 2015 14:26:05 -0700 (PDT) In-Reply-To: <551074C8.10306@gmail.com> References: <550EC85E.7070206@gmail.com> <551074C8.10306@gmail.com> Date: Mon, 23 Mar 2015 18:26:05 -0300 Message-ID: Subject: Re: [lojban] On the meanings of the causal gismu From: =?UTF-8?Q?Jorge_Llamb=C3=ADas?= To: lojban@googlegroups.com Content-Type: multipart/alternative; boundary=047d7bb041024d183d0511fb50c6 X-Original-Sender: jjllambias@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jjllambias@gmail.com designates 2a00:1450:400c:c05::236 as permitted sender) smtp.mail=jjllambias@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=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-Unsubscribe: , X-Spam-Score: -1.7 (-) X-Spam_score: -1.7 X-Spam_score_int: -16 X-Spam_bar: - --047d7bb041024d183d0511fb50c6 Content-Type: text/plain; charset=UTF-8 On Mon, Mar 23, 2015 at 5:17 PM, Ilmen wrote: > I've always though of {selja'e} as being a somewhat looser / less strict > relation than {rinka}, as if it was something like {x1 .a lo selpau be x1 > cu rinka x2}, so that one can say {lo nu carvi cu selja'e lo nu mi na > klama}, where the connection between the two events is not clearly > explained, and where it seems that "lo nu carvi" is not the only factor > that have determined the event {lo nu mi klama} not to occur (another > plausible factor could be "mi na djica lo nu mi se carvi"). > But this impression that {selja'e} is looser than {rinka} is perhaps > subjective, and maybe {rinka} can be used just as vaguely. > Maybe, but the distinction would still be blurry, because giving an exhaustive description of the full cause of anything is nearly impossible, so we always really just give the main and most significant factors. lo nu carvi and lo nu mi na djica lo nu mi se carvi cannot be the full factors that cause lo nu mi na klama, because under the right circumstances lo nu mi klama could still happen in spite of those causes, so there's always an implicit "under conditions" that collects all the things taken for granted. > "banzu" is not the same as "rinka". ro da zo'u da banzu da .i ku'i na ku > ro da zo'u da rinka da .i la'a no da zo'u da rinka da .i ro da poi kacna'u > zo'u lo du'u da pilji li vo lo kacna'u cu banzu lo du'u da pilji li re lo > kacna'u .i ku'i pe'i lo du'u pilji li vo cu na rinka lo du'u pilji li re > > But, isn't this second example (that with {kacna'u}) what {nibli} is for? > I thought that banzu-nu (the version of {banzu} that parallels {sarcu}) was > the event equivalent of {nibli}. > We could also use "nibli" there, but I don't see a problem with "banzu". If p entails q then p is a sufficient condition for q. But let's discard this example if you prefer. mu'o mi'e xorxes -- 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. For more options, visit https://groups.google.com/d/optout. --047d7bb041024d183d0511fb50c6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Mon, Mar 23, 2015 at 5:17 PM, Ilmen <ilmen.pokebip@gmail.com&= gt; wrote:
=20 =20 =20
I've always though of {selj= a'e} as being a somewhat looser / less strict relation than {rinka}, as if it was something like {x1 .a lo selpau be x1 cu rinka x2}, so that one can say {lo nu carvi cu selja'e lo nu mi na klama}, where the connection between the two events is not clearly explained, and where it seems that "lo nu carvi" is not the only factor that have determined the event {lo n= u mi klama} not to occur (another plausible factor could be "mi na djica lo nu mi se carvi").
But this impression that {selja'e} is looser than {rinka} is perhap= s subjective, and maybe {rinka} can be used just as vaguely.

Maybe, but the distinction would still be blurry,= because giving an exhaustive description of the full cause of anything is = nearly impossible, so we always really just give the main and most signific= ant factors. lo nu carvi and lo nu mi na djica lo nu mi se carvi cannot be = the full factors that cause lo nu mi na klama, because under the right circ= umstances lo nu mi klama could still happen in spite of those causes, so th= ere's always an implicit "under conditions" that collects all= the things taken for granted.
"banzu" is not the same as "rinka". ro da zo'u d= a banzu da .i ku'i na ku ro da zo'u da rinka da .i la'a n= o da zo'u da rinka da .i ro da poi kacna'u zo'u lo du'u da = pilji li vo lo kacna'u cu banzu lo du'u da pilji li re lo kacn= a'u .i ku'i pe'i lo du'u pilji li vo cu na rinka lo d= u'u pilji li re
But, isn't this second example (that with {kacna'u}) what {nibl= i} is for? I thought that banzu-nu (the version of {banzu} that parallels {sarcu}) was the event equivalent of {nibli}.

We could also use "nibli" there, but I don't= see a problem with "banzu". If p entails q then p is a sufficien= t condition for q. But let's discard this example if you prefer.
<= div>
mu'o mi'e xorxes

--
You received this message because you are subscribed to the Google Groups &= quot;lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to lojban+unsub= scribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http:= //groups.google.com/group/lojban.
For more options, visit http= s://groups.google.com/d/optout.
--047d7bb041024d183d0511fb50c6--