From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: flyspell bug Date: Thu, 12 May 2005 21:34:06 -0400 Message-ID: References: <01c5531e$Blat.v2.4$ea8d9a00@zahav.net.il> <87zmv3rg09.fsf_-_@jurta.org> <877ji5vypt.fsf@jurta.org> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1115948003 30601 80.91.229.2 (13 May 2005 01:33:23 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 13 May 2005 01:33:23 +0000 (UTC) Cc: public@heslin.eclipse.co.uk, mange@freemail.hu, s.j.eglen@damtp.cam.ac.uk, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 13 03:33:21 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DWP3F-0006nV-0d for ged-emacs-devel@m.gmane.org; Fri, 13 May 2005 03:33:17 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DWPCI-0007OF-1z for ged-emacs-devel@m.gmane.org; Thu, 12 May 2005 21:42:38 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DWPBK-0006x3-Bs for emacs-devel@gnu.org; Thu, 12 May 2005 21:41:38 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DWPBD-0006td-Oe for emacs-devel@gnu.org; Thu, 12 May 2005 21:41:32 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DWPBB-0006pW-Gb for emacs-devel@gnu.org; Thu, 12 May 2005 21:41:29 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DWPCL-0001Va-6h for emacs-devel@gnu.org; Thu, 12 May 2005 21:42:41 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1DWP42-0001zE-FE; Thu, 12 May 2005 21:34:06 -0400 Original-To: Juri Linkov In-reply-to: <877ji5vypt.fsf@jurta.org> (message from Juri Linkov on Thu, 12 May 2005 08:28:45 +0300) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:37053 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:37053 However, the installed change is too radical. It affects all users of ispell having aspell in exec-path. Preferring aspell to ispell will inevitably do that. It is the price that must be paid for a change that we will make sooner or later. We are going to switch to preferring aspell sometime. If aspell is not ready, we can't do it. If aspell is ready now, sooner is better than later. If switching from ispell to aspell was intentional (I can't find a discussion about this on emacs-devel) then we need to document it in the NEWS file with a warning about possible problems, to inform maintainers of ispell.el and aspell about this change asking them to update documentation, web pages, and to test aspell dictionaries to confirm their compatibility with ispell.el. We're not building airplanes, you know. Ideally in the absence of resource constraints we would do all these things, but we don't have to do them all. We should not evaluate development choices as if we were going to do them with the level of care that would be required for building airplanes. But perhaps switching from ispell to aspell was too hasty change. According to aspell's TODO list, ispell.el is not quite ready for using aspell. I would not rely on aspell's TODO list for the very latest information on the status of ispell.el development. The facts we are observing directly about ispell are much more authoritative than a report that might be old.