Return-path: Envelope-to: rlpowell@digitalkingdom.org Delivery-date: Mon, 14 Aug 2006 14:06:21 -0700 Received: from chain.digitalkingdom.org ([64.81.49.134]) by chain.digitalkingdom.org with esmtp (Exim 4.62) (envelope-from ) id 1GCjdC-0008HY-AG; Mon, 14 Aug 2006 14:05:56 -0700 Received: with ECARTIS (v1.0.0; list jbovlaste); Mon, 14 Aug 2006 14:05:52 -0700 (PDT) Received: from nobody by chain.digitalkingdom.org with local (Exim 4.62) (envelope-from ) id 1GCjd9-0008HS-TI for jbovlaste-real@lojban.org; Mon, 14 Aug 2006 14:05:52 -0700 Received: from miranda.org ([216.93.242.2]) by chain.digitalkingdom.org with smtp (Exim 4.62) (envelope-from ) id 1GCjd6-0008HK-Ut for jbovlaste@lojban.org; Mon, 14 Aug 2006 14:05:51 -0700 Received: (qmail 7317 invoked by uid 534); 14 Aug 2006 15:05:47 -0600 Date: Mon, 14 Aug 2006 15:05:47 -0600 From: Jay F Kominek To: jbovlaste@lojban.org Subject: [jbovlaste] Re: Incorrect use of subsenses, how to remove (and permanent fix?) Message-ID: <20060814210547.GQ27480@miranda.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i X-Spam-Score: -2.5 (--) X-ecartis-version: Ecartis v1.0.0 Sender: jbovlaste-bounce@lojban.org Errors-to: jbovlaste-bounce@lojban.org X-original-sender: jkominek@miranda.org Precedence: bulk Reply-to: jbovlaste@lojban.org X-list: jbovlaste X-Spam-Score: -2.5 (--) Content-Length: 915 Lines: 26 On Sun, Aug 13, 2006 at 04:33:28PM +0200, Arnt Richard Johansen wrote: > If I understand it correctly, "editing" a natlang word doesn't really > edit the word object per se, but rather creates a new one, updating > all the pointers to it in the process. That might explain why he got that message. At one point, as I'm sure you remember, it wasn't possible at all to have the natlang word with and without a sense. There might still be a check in that editing stuff which is left over from that. > Right now, I would like to have the subsenses in the following natlang > words removed: Done. Check to make sure I didn't screw it up. > Also, I would like some way of fixing this kind of error without having > database access. Me too. Somebody just needs to write up and debug a little edit page, I guess. Or fix the existing one if I'm right about it having a bug. -- Jay Kominek