From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: VC filesets Date: Sun, 19 Oct 2008 23:04:55 -0700 Message-ID: <006801c93279$c802fb40$0200a8c0@us.oracle.com> References: <87hc795llv.fsf@cyd.mit.edu> <005b01c93232$adfb7020$0200a8c0@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1224507750 2433 80.91.229.12 (20 Oct 2008 13:02:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 20 Oct 2008 13:02:30 +0000 (UTC) Cc: rgm@gnu.org, cyd@stupidchicken.com, emacs-devel@gnu.org To: Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 20 15:03:17 2008 connect(): Connection refused 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 1Krntq-0002Dz-0B for ged-emacs-devel@m.gmane.org; Mon, 20 Oct 2008 08:05:54 +0200 Original-Received: from localhost ([127.0.0.1]:56119 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Krnsk-0007VA-JY for ged-emacs-devel@m.gmane.org; Mon, 20 Oct 2008 02:04:46 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Krnsg-0007V5-Fg for emacs-devel@gnu.org; Mon, 20 Oct 2008 02:04:42 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Krnse-0007Ut-PN for emacs-devel@gnu.org; Mon, 20 Oct 2008 02:04:41 -0400 Original-Received: from [199.232.76.173] (port=53239 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Krnse-0007Uq-NA for emacs-devel@gnu.org; Mon, 20 Oct 2008 02:04:40 -0400 Original-Received: from rgminet01.oracle.com ([148.87.113.118]:60923) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Krnsb-0003QC-T9; Mon, 20 Oct 2008 02:04:38 -0400 Original-Received: from agmgw1.us.oracle.com (agmgw1.us.oracle.com [152.68.180.212]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id m9K64YjG026845; Mon, 20 Oct 2008 00:04:35 -0600 Original-Received: from acsmt707.oracle.com (acsmt707.oracle.com [141.146.40.85]) by agmgw1.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id m9K64Y1L024785; Mon, 20 Oct 2008 00:04:34 -0600 Original-Received: from dradamslap1 (/24.23.165.218) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 20 Oct 2008 06:04:34 +0000 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Thread-Index: AckydNeCI29vef1PQs2AUDZse+KBdQAAdk5w X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 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:104660 Archived-At: > The idea was that filesets.el would be a general facility for > file sets and that we would make other things work with it. Yes, I realize that. But it is not that general. And things haven't really worked out that way. And regardless of what one might think of that particular example, the general terminology issues that were raised remain. It doesn't matter, for example, that bookmarks.el *is* quite general and could be extended to include things that might be found in other "bookmarks" libraries available here and there. Independent libraries get developed with different or similar features - or even virtually identical features that are implemented differently. In many cases they will always remain separate, rather than being incorporated (into bookmarks.el for example). The problems I raised are (only) about terminology, not about implementation, features, or packaging. It's about how to talk about features, not about how to integrate or assimilate them. Using more specific names can help avoid some of the problems. Using file names that are different from general feature names can help too. But I don't see a general solution to the terminology problems. In the case Glenn initially raised, VC filesets, presumably a solution could be found, because VC filesets and filesets.el filesets are both part of Emacs. I take his observation as a suggestion that VC filesets should be called something else. That would take care of this particular occurrence of the problem. Or perhaps, following your remark above, VC filesets should be somehow integrated with filesets.el filesets, since the latter feature is the intended "general facility for file sets". I can't speak to that, knowing nothing about VC filesets.