From pycyn@aol.com Sat Aug 18 15:01:38 2001 Return-Path: X-Sender: Pycyn@aol.com X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-7_3_1); 18 Aug 2001 22:01:38 -0000 Received: (qmail 4990 invoked from network); 18 Aug 2001 22:01:37 -0000 Received: from unknown (10.1.10.27) by m8.onelist.org with QMQP; 18 Aug 2001 22:01:37 -0000 Received: from unknown (HELO imo-r08.mx.aol.com) (152.163.225.104) by mta2 with SMTP; 18 Aug 2001 22:01:37 -0000 Received: from Pycyn@aol.com by imo-r08.mx.aol.com (mail_out_v31_r1.4.) id r.12a.2fc946e (3928) for ; Sat, 18 Aug 2001 18:01:34 -0400 (EDT) Message-ID: <12a.2fc946e.28b03fbe@aol.com> Date: Sat, 18 Aug 2001 18:01:34 EDT Subject: Re: [lojban] mo To: lojban@yahoogroups.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_12a.2fc946e.28b03fbe_boundary" X-Mailer: AOL 6.0 for Windows US sub 10531 From: pycyn@aol.com --part1_12a.2fc946e.28b03fbe_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_12a.2fc946e.28b03fbe_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_12a.2fc946e.28b03fbe_boundary--