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: What a modern collaboration toolkit looks like Date: Sun, 06 Jan 2008 03:09:53 -0500 Message-ID: References: <20071230122217.3CA84830B9A@snark.thyrsus.com> <20071231130712.GB8641@thyrsus.com> <20071231214108.GD26639@thyrsus.com> <200801010027.m010R74P025484@oogie-boogie.ics.uci.edu> <20071231190034.12b0ed4a@reforged> <20080104193421.0d4091ea@reforged> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: ger.gmane.org 1199607279 28885 80.91.229.12 (6 Jan 2008 08:14:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 6 Jan 2008 08:14:39 +0000 (UTC) Cc: emacs-devel@gnu.org To: Mike Mattie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 06 09:15:00 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JBQeo-00017j-TW for ged-emacs-devel@m.gmane.org; Sun, 06 Jan 2008 09:14:59 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBQeR-0001YY-Ky for ged-emacs-devel@m.gmane.org; Sun, 06 Jan 2008 03:14:35 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JBQeM-0001V1-QY for emacs-devel@gnu.org; Sun, 06 Jan 2008 03:14:30 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JBQeL-0001U0-E6 for emacs-devel@gnu.org; Sun, 06 Jan 2008 03:14:30 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBQeL-0001Tx-7j for emacs-devel@gnu.org; Sun, 06 Jan 2008 03:14:29 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JBQeL-0004Jk-4G for emacs-devel@gnu.org; Sun, 06 Jan 2008 03:14:29 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1JBQZt-0001e9-FC; Sun, 06 Jan 2008 03:09:53 -0500 In-reply-to: <20080104193421.0d4091ea@reforged> (message from Mike Mattie on Fri, 4 Jan 2008 19:34:21 -0800) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:86293 Archived-At: So split the setup means break up the user's .emacs file into parts: config/ .emacs style/ -> spell.el ; spell features -> lisp.el ; lisp programming features the .emacs file is carefully coded to make sure that it has a low risk of errors. Note that the style directory is not included in load-path deliberately. We ask people not to start off beginners with a customized Emacs. A new users should learn a standard Emacs, and then customize it if he wants to customize it. But he shouldn't be led into using something nonstandard before he knows the difference. In this case turning on, adding, and customizing the various spelling features of Emacs to the point where spelling support is pervasive and well integrated constitutes a modular style of using Emacs. Do you think that enabling the spelling features of Emacs is complex? If so, maybe we should simplify it. That would be a better solution to this problem, if it exists. each of these large customization files such as spell.el have this basic fo= rm: phase 1: define a installer phase 2: check dependencies with require phase 3: perform customization Why is so much needed just to enable spelling features? 1. User request's some help getting their Emacs setup with some of Bob's (G= uru) features. 2. User receives The Guru's modular configuration and installs it. If "Bob's features" refers to Lisp packages not included in Emacs, then why not install them in the standard directory on the user's machine? There `load-library' will find them without any special effort.