From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: Files in wrong subdirs of emacs/lisp? Date: Wed, 21 May 2003 15:02:42 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <20030521145131.30A4.JMBARRANQUERO@laley.wke.es> References: <20030521101542.4DB2.JMBARRANQUERO@laley.wke.es> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: main.gmane.org 1053523059 20271 80.91.224.249 (21 May 2003 13:17:39 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 21 May 2003 13:17:39 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed May 21 15:17:36 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19ITQF-00050O-00 for ; Wed, 21 May 2003 15:14:23 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 19ITb2-0007UH-00 for ; Wed, 21 May 2003 15:25:32 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19ITKl-0003Rg-J5 for emacs-devel@quimby.gnus.org; Wed, 21 May 2003 09:08:43 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19ITJu-00031H-ID for emacs-devel@gnu.org; Wed, 21 May 2003 09:07:50 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19ITFh-0000a1-Pz for emacs-devel@gnu.org; Wed, 21 May 2003 09:03:30 -0400 Original-Received: from laley-actualidad.es ([195.53.61.17] helo=haya.laley.net) by monty-python.gnu.org with esmtp (Exim 4.20) id 19ITDT-0000NN-GO for emacs-devel@gnu.org; Wed, 21 May 2003 09:01:11 -0400 Original-Received: from idefix.laley.net (correo.wke.es [172.17.220.16]) by haya.laley.net (8.9.3/8.9.3) with ESMTP id OAA29106; Wed, 21 May 2003 14:59:01 +0200 Original-Received: from [172.17.2.45] (JMBARRANQUERO [172.17.2.45]) by idefix.laley.net 5.5.2655.55) id LHASQNNA; Wed, 21 May 2003 15:02:08 +0200 Original-To: bob@rattlesnake.com In-Reply-To: X-Mailer: Becky! ver. 2.06.02 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Emacs development discussions. List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:14038 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:14038 On Wed, 21 May 2003 08:32:00 -0400 (EDT) "Robert J. Chassell" wrote: > Why is it so hard to imagine? A lack of imagination on my part, I suppose :) > My understanding is that some of the currently popular small devices > do not support floating point. I do not know for sure, but if true, > then potentially, millions of people could use such an Emacs. >=20 > (These small machines do not have much capacity, so I imagine that > developers would include just those parts of Emacs that they need. At > one point, I reduced the Emacs 18 footprint to 300 kilobytes for a > version that did what *I* mostly used. So I know that Emacs can be > made small, and still be useable. Yes, if Emacs were to be compiled for Windows CE, Windows for Smartphone, Symbian, EPOC or PalmOS, checking for floating-point support would be useful. I'd bet, though, that these systems (and the hardware they run on) will support floating point long before someone takes the pain to trying compiling Emacs for them... You're talking about Emacs 18, and the changes in the CVS are for Emacs 22 (or 21.5 at the very least). I don't think the current CVS sources are nowhere near configurable enough to be easily downsized to such small machines... And if posible, well, lisp/obsolete/float-sup.el is not much farther away than lisp/float-sup.el, isn't it? Just my .02=80 Juanma Note: However, I must insist again: My list wasn't "hey, guys, let's go obsolete these modules", but more like "hey, does someone know if they're still useful and maintained?" I have no interest whatsoever in obsoleting or not obsoleting any of them, other than tidying up the current lisp/ hierarchy.