Return-path: X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on chain.digitalkingdom.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS, T_DKIM_INVALID,T_TO_NO_BRKTS_FREEMAIL autolearn=ham version=3.3.1 X-Spam-Personal-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on chain.digitalkingdom.org Envelope-to: rlpowell@digitalkingdom.org Delivery-date: Fri, 17 Dec 2010 10:15:51 -0800 Received: from chain.digitalkingdom.org ([192.168.123.127]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1PTep8-0000uV-Lc; Fri, 17 Dec 2010 10:14:34 -0800 Received: with ECARTIS (v1.0.0; list jbovlaste); Fri, 17 Dec 2010 10:13:41 -0800 (PST) Received: from nobody by chain.digitalkingdom.org with local (Exim 4.72) (envelope-from ) id 1PTeoG-0000uO-BJ for jbovlaste-real@lojban.org; Fri, 17 Dec 2010 10:13:40 -0800 Received: from mail-fx0-f52.google.com ([209.85.161.52]) by chain.digitalkingdom.org with esmtp (Exim 4.72) (envelope-from ) id 1PTeoC-0000ts-MF for jbovlaste@lojban.org; Fri, 17 Dec 2010 10:13:40 -0800 Received: by fxm5 with SMTP id 5so878808fxm.11 for ; Fri, 17 Dec 2010 10:13:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=967I22lclhASAiNzycN2L3rewmKYqPifXqZLA0pWvgw=; b=t3s80gErwWgOrt+MhwBEn9VmqHd4ZUL7mxKf+UlH+dLljosQANTLmvOukp1hFeygTO Dg1pIrTl0yVtW6bD3dtZXUpE86ocbA5LC9PG7X/74FjKLCe/9Hvui+Q0PhtPFXFnKsgm tVh5oEInhydnIGw2CoMqtvFhaA5CQJZDV/gho= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=nIqUK6Isaw3JYzDl8hHlt9RFJ5ueHyajyNuX6l86DmW6xkDJh0+YJAr9LDayh9mEfb pJ2bmGYTqPQ8ZOuPAcQkts9KNfdNxxE3d5mkaMrXMF1gQhE5aG+xN8248GYcFrFfcZ+C rfJw5cRhGh7NUJrg7obQrKMRlbMJ2CEmKoBMw= Received: by 10.223.120.78 with SMTP id c14mr1454859far.14.1292609610186; Fri, 17 Dec 2010 10:13:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.66.220 with HTTP; Fri, 17 Dec 2010 10:13:10 -0800 (PST) In-Reply-To: References: <20101217161949.GI32499@alice.local> From: Oren Date: Fri, 17 Dec 2010 13:13:10 -0500 Message-ID: Subject: [jbovlaste] Re: defining "debug" To: jbovlaste@lojban.org Content-Type: multipart/alternative; boundary=0016e68ef09ba6158204979f2010 X-ecartis-version: Ecartis v1.0.0 Sender: jbovlaste-bounce@lojban.org Errors-to: jbovlaste-bounce@lojban.org X-original-sender: get.oren@gmail.com Precedence: bulk Reply-to: jbovlaste@lojban.org X-list: jbovlaste Content-Length: 2761 Lines: 75 --0016e68ef09ba6158204979f2010 Content-Type: text/plain; charset=ISO-8859-1 I'm moving this to another subject line on jbovlaste so as not to distract the conversation about lujvo pragmatics :) On Fri, Dec 17, 2010 at 11:51, Oren wrote: > when I { troci }, i think of it as an effort/attempt at something, whereas > when i think of "trying something out" i.e. giving a car a test drive, or > running a program to see some output, i see that as something more like { > cipra } or pajni or jarco, I'm verifying some parameter that's in question, > > ex. > { mi troci lonu sazri lo karce } > I'm trying to drive a car, as in > I'm attempting/making an effort to attain driving a car. > > { mi cipra lo spofu lo karce } ? > I'm trying out the car, as in > I'm taking a car for a test drive to see if/how it's broken. > > (I probably said those wrong) > > So maybe troci isn't the right thing to integrate into "debugging"? How > about { cipra cikre } for test-fix? > -- Oren Robinson (315) 569-2888 102 Morrison Ave Somerville, MA 02144 --0016e68ef09ba6158204979f2010 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I'm moving this to another subject line on jbovlaste s= o as not to distract the conversation about lujvo pragmatics :)

On Fri, Dec 17, 2010 at 11:51, Oren <get.oren@gmail.com> wrote:
when I { troci }, i think of it as an = effort/attempt at something, whereas when i think of "trying something= out" i.e. giving a car a test drive, or running a program to see some= output, i see that as something more like { cipra } or pajni or jarco, I&#= 39;m verifying some parameter that's in question,

ex.
{ mi troci lonu sazri lo karce }
I'= ;m trying to drive a car, as in
I'm attempting/making an effo= rt to attain driving a car.

{ mi cipra lo spofu lo= karce } ?
I'm trying out the car, as in
I'm taking a car for a= test drive to see if/how it's broken.

(I prob= ably said those wrong)

So maybe troci isn't th= e right thing to integrate into "debugging"? How about { cipra ci= kre } for test-fix?



--
Oren R= obinson
(315) 569-2888
102 Morrison Ave
Somerville,= MA 02144

--0016e68ef09ba6158204979f2010--