From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel,gmane.emacs.multi-tty Subject: Re: Merging multitty Date: Fri, 11 May 2007 13:01:16 +0200 Message-ID: <86y7jv1v5v.fsf@lola.quinscape.zz> References: <2wmz0iriyj.fsf@fencepost.gnu.org> <87fy65k6eh.fsf@red-bean.com> <853b25lk43.fsf@lola.goethe.zz> <86bqgr3g1h.fsf_-_@lola.quinscape.zz> <4644355E.7070004@gnu.org> <867irf3cjo.fsf@lola.quinscape.zz> <464444AF.9070905@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1178881295 8415 80.91.229.12 (11 May 2007 11:01:35 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 11 May 2007 11:01:35 +0000 (UTC) Cc: multi-tty@fnord.hu, emacs-devel@gnu.org, karoly@lorentey.hu, rms@gnu.org, Kenichi Handa To: Jason Rumney Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 11 13:01:31 2007 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 1HmSsN-0007NU-6i for ged-emacs-devel@m.gmane.org; Fri, 11 May 2007 13:01:31 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HmSzm-00053h-HB for ged-emacs-devel@m.gmane.org; Fri, 11 May 2007 07:09:10 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HmSzg-00052I-BP for emacs-devel@gnu.org; Fri, 11 May 2007 07:09:04 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HmSzc-0004yz-AR for emacs-devel@gnu.org; Fri, 11 May 2007 07:09:01 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HmSzc-0004yi-49 for emacs-devel@gnu.org; Fri, 11 May 2007 07:09:00 -0400 Original-Received: from pc3.berlin.powerweb.de ([62.67.228.11]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HmSsB-000336-Q5 for emacs-devel@gnu.org; Fri, 11 May 2007 07:01:20 -0400 Original-Received: from quinscape.de (pd95b0fdb.dip0.t-ipconnect.de [217.91.15.219]) by pc3.berlin.powerweb.de (8.9.3p3/8.9.3) with ESMTP id NAA03480 for ; Fri, 11 May 2007 13:01:14 +0200 X-Delivered-To: Original-Received: (qmail 6348 invoked from network); 11 May 2007 11:01:16 -0000 Original-Received: from unknown (HELO lola.quinscape.zz) ([10.0.3.43]) (envelope-sender ) by ns.quinscape.de (qmail-ldap-1.03) with SMTP for ; 11 May 2007 11:01:16 -0000 Original-Received: by lola.quinscape.zz (Postfix, from userid 1001) id 983528F998; Fri, 11 May 2007 13:01:16 +0200 (CEST) In-Reply-To: <464444AF.9070905@gnu.org> (Jason Rumney's message of "Fri\, 11 May 2007 11\:25\:51 +0100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.91 (gnu/linux) X-detected-kernel: 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:70799 gmane.emacs.multi-tty:680 Archived-At: Jason Rumney writes: > David Kastrup wrote: > >> I disagree with that assessment. It presumes that not making Emacs >> multitty-capable ever is a reasonable option. > > It is the only option if we don't have anyone willing to maintain > that capability. But judging from your activism on this, I don't > expect we will have that problem. My "activism" does not make me a Windows, DOS, or MacOSX developer, so it would not carry the day. While I don't remember a "horribly broken" assessment either, it does not seem like I have the most reliable of recollections about the details of the discussion. I think it is more or less safe to say that it is about time to have multitty moved into at least a branch in Emacs-CVS since development in its own repository has IIRC been reduced mostly to synches, anyway. Since its current version control system is arch-based, it sounds like the way through the arch-variant of Emacs CVS that Miles proposed would likely be the best way to do this: the person doing the move would then work with a system he is familiar with on both ends. -- David Kastrup