From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/24434 Path: main.gmane.org!not-for-mail From: Hrvoje Niksic Newsgroups: gmane.emacs.gnus.general Subject: Re: off topic alert: XEmacs vs Emacs? Date: 21 Jul 1999 13:00:01 +0200 Sender: owner-ding@hpc.uh.edu Message-ID: <87vhbegte6.fsf@pc-hrvoje.srce.hr> References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1035161999 8646 80.91.224.250 (21 Oct 2002 00:59:59 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 00:59:59 +0000 (UTC) Return-Path: Original-Received: from farabi.math.uh.edu (farabi.math.uh.edu [129.7.128.57]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id HAA09991 for ; Wed, 21 Jul 1999 07:00:47 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by farabi.math.uh.edu (8.9.1/8.9.1) with ESMTP id GAB28098; Wed, 21 Jul 1999 06:00:35 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Wed, 21 Jul 1999 06:01:22 -0500 (CDT) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id GAA13321 for ; Wed, 21 Jul 1999 06:01:13 -0500 (CDT) Original-Received: from pc-hrvoje.srce.hr (mail@pc-hrvoje.srce.hr [161.53.2.132]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id HAA09983 for ; Wed, 21 Jul 1999 07:00:07 -0400 (EDT) Original-Received: from hniksic by pc-hrvoje.srce.hr with local (Exim 3.02 #1 (Debian)) id 116u6W-0000RY-00 for ; Wed, 21 Jul 1999 13:00:04 +0200 Original-To: ding@gnus.org X-Attribution: Hrvoje X-Face: &{dT~)Pu6V<0y?>3p$;@vh\`C7xB~A0T-J%Og)J,@-1%q6Q+, gs<-9M#&`I8cJp2b1{vPE|~+JE+gx;a7%BG{}nY^ehK1"q#rG O,Rn1A_Cy%t]V=Brv7h writes: > On the other hand, I see that XEmacs behaves in, err, /unexpected/ > ways. Two anecdotical examples: loading del-bs.el (or similar) does > what one expect, *except* in Lisp Interaction mode. Hm. rcp.el > doesn't work together with EFS because EFS expects to be the only > remote-file handling package used (well, the only one which uses > file names beginning with "/foo:"). > > I get a vague feeling that the many packages included with XEmacs > might not be so well thought-out and thoroughly-tested. Have you considered actually reporting a bug? I don't know what "packages included with XEmacs" means to you, so I can't comment if they are "so well thought-out and thoroughly-tested". I do know that the XEmacs development process is just as thorough as the FSF one. It often happens that the FSF code is debugged before it's included in XEmacs, or that it's simply not included because of its inferior quality. The reverse also happens -- bad code gets introduced to XEmacs and it needs fixing. But that's not an inherent fault of XEmacs. If you wish to try XEmacs *seriously*, try it. If you find a bug, report it or, better yet, try to fix it. You have the knowledge. > If you feel this discussion is inappropriate in this group, feel > free to say so and I'll go elsewhere. So.