From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.help Subject: Re: Gnu Emacs and gnuclient Date: Thu, 22 Feb 2007 21:56:58 +0100 Organization: Organization?!? Message-ID: <851wkhewrp.fsf@lola.goethe.zz> References: <1172165717.774368.79760@s48g2000cws.googlegroups.com> <87slcy3tsi.fsf@post.rwth-aachen.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1172180447 24199 80.91.229.12 (22 Feb 2007 21:40:47 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 22 Feb 2007 21:40:47 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Feb 22 22:40:41 2007 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HKLg8-0005ao-Cd for geh-help-gnu-emacs@m.gmane.org; Thu, 22 Feb 2007 22:40:40 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HKLg7-0003FV-QU for geh-help-gnu-emacs@m.gmane.org; Thu, 22 Feb 2007 16:40:39 -0500 Original-Path: shelby.stanford.edu!headwall.stanford.edu!newsfeed.news2me.com!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsfeed.arcor.de!newsspool1.arcor-online.net!news.arcor.de.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.help X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.93 (gnu/linux) Cancel-Lock: sha1:sNivko+0g65utiT6g9zkrkKytF4= Original-Lines: 39 Original-NNTP-Posting-Date: 22 Feb 2007 21:56:58 CET Original-NNTP-Posting-Host: d57531b4.newsspool1.arcor-online.net Original-X-Trace: DXC=bQ=ALDEEOh[\PS5Xo=M[RVic==]BZ:af^4Fo<]lROoRQFl8W>\BH3YRnn>]N_\:jO_CV`H8_`hhQT^9QSCVg3dOVOIC5DBZVJ9[b@LoDFJCQEU\V:T<3eAOF^ Original-X-Complaints-To: usenet-abuse@arcor.de Original-Xref: shelby.stanford.edu gnu.emacs.help:145813 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:41417 Archived-At: Thorsten Bonow writes: > I *love* the Multi-tty features. If the XEmacs team doesn't get > their act together any time soon, I will do the switch away from my > beloved XEmacs because of this feature alone (Sigh). Uh, what? The whole point of the awfully overdesigned locale/specifier/instantiator system in XEmacs that has from the beginning made it impossible for anybody but the very gifted to actually program and/or understand code seriously making use of images and toolbars has been the support of multiple ttys with different capabilities. Consequently, XEmacs' gnuclient can open a frame right in the gnuclient tty. It's been a selling point of XEmacs for decades, actually. Now as far as I can tell, the programming APIs of Emacs' multi-tty support will be much much easier to understand and use. But the basic _feature_ has, as far as I can judge, been available to users pretty much from the beginning of Lucid Emacs' separate existence. I can't think of any feature gap that took Emacs longer to close. So as long as you are talking about the user-level feature (and not the programmers' API), I am somewhat at a loss about why this would make you consider a switch. I am certainly not above XEmacs-bashing, but I would not have thought user-level multi-tty support a suitable area. It's been around in XEmacs from very early on as far as I can tell. So could you elaborate? -- David Kastrup, Kriemhildstr. 15, 44793 Bochum