From pycyn@aol.com Sat Aug 18 15:04:54 2001 Return-Path: X-Sender: Pycyn@aol.com X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-7_3_1); 18 Aug 2001 22:04:54 -0000 Received: (qmail 51980 invoked from network); 18 Aug 2001 22:04:53 -0000 Received: from unknown (10.1.10.142) by l8.egroups.com with QMQP; 18 Aug 2001 22:04:53 -0000 Received: from unknown (HELO imo-d09.mx.aol.com) (205.188.157.41) by mta3 with SMTP; 18 Aug 2001 22:04:53 -0000 Received: from Pycyn@aol.com by imo-d09.mx.aol.com (mail_out_v31_r1.4.) id r.10f.400d7c9 (4540) for ; Sat, 18 Aug 2001 18:04:47 -0400 (EDT) Message-ID: <10f.400d7c9.28b0407f@aol.com> Date: Sat, 18 Aug 2001 18:04:47 EDT Subject: Re: [lojban] mo To: lojban@yahoogroups.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_10f.400d7c9.28b0407f_boundary" X-Mailer: AOL 6.0 for Windows US sub 10531 From: pycyn@aol.com --part1_10f.400d7c9.28b0407f_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Strictly speaking, {mo} is a *bridi* question and picks up selbri and brivla as degenerate cases (the most common, perhaps, as often in weird little societies like Lojbnaistan). Thus viewed, {mo mo} don't make no mo' sense, as does not two bridi run together without a connective. That said (look Ma, and ablative absolute!), one might argue that {mo mo} does have a real use in the language, perhaps to indicate how specific and answer is expected -- with three, or even five, levels of specification. But that is strictly an idiom, though a reasonably clear one in the circumstances. --part1_10f.400d7c9.28b0407f_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: 7bit Strictly speaking, {mo} is a *bridi*  question and picks up selbri and brivla
as degenerate cases (the most common, perhaps, as often in weird little
societies like Lojbnaistan).  Thus viewed, {mo mo} don't make no mo' sense,
as does not two bridi run together without a connective.  
That said (look Ma, and ablative absolute!), one might argue that {mo mo}
does have a real use in the language, perhaps to indicate how specific and
answer is expected -- with three, or even five, levels of specification.  But
that is strictly an idiom, though a reasonably clear one in the circumstances.
--part1_10f.400d7c9.28b0407f_boundary--