From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: (featurep 'multi-tty) => t on Windows Date: Fri, 12 Dec 2008 07:01:05 -0500 Message-ID: References: <610112.22856.qm@web83202.mail.mud.yahoo.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1229083332 4390 80.91.229.12 (12 Dec 2008 12:02:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 12 Dec 2008 12:02:12 +0000 (UTC) Cc: cyd@stupidchicken.com, pandyacus@sbcglobal.net, emacs-devel@gnu.org To: "Juanma Barranquero" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 12 13:03:16 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 1LB6ja-0000DO-I9 for ged-emacs-devel@m.gmane.org; Fri, 12 Dec 2008 13:03:06 +0100 Original-Received: from localhost ([127.0.0.1]:48438 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LB6iP-0001A5-08 for ged-emacs-devel@m.gmane.org; Fri, 12 Dec 2008 07:01:53 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LB6iJ-000192-1a for emacs-devel@gnu.org; Fri, 12 Dec 2008 07:01:47 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LB6iH-00018I-Ac for emacs-devel@gnu.org; Fri, 12 Dec 2008 07:01:46 -0500 Original-Received: from [199.232.76.173] (port=50567 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LB6iH-00017v-0c for emacs-devel@gnu.org; Fri, 12 Dec 2008 07:01:45 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]:48616) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LB6iG-0004qX-Fr for emacs-devel@gnu.org; Fri, 12 Dec 2008 07:01:44 -0500 Original-Received: from eliz by fencepost.gnu.org with local (Exim 4.67) (envelope-from ) id 1LB6hd-0007PC-4F; Fri, 12 Dec 2008 07:01:05 -0500 In-reply-to: (lekktu@gmail.com) X-detected-operating-system: by monty-python.gnu.org: GNU/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:106837 Archived-At: > Date: Fri, 12 Dec 2008 00:39:10 +0100 > From: "Juanma Barranquero" > Cc: pandyacus@sbcglobal.net, cyd@stupidchicken.com, emacs-devel@gnu.org > > The point is, IMHO, that (featurep 'multi-tty) will allow the code to > have some expectations, like the possibility of having simultaneous > tty and GUI frames Code that assumes such a possibility without testing for (featurep 'x) (or something similar for Windows) is buggy and should be fixed. One can build Emacs --without-x, in which case it cannot have both tty and GUI frames. But such an Emacs is still multi-tty, since it can have multiple tty frames. > that currently the Windows port can not satisfy. I think the situation on Windows is worse: there are some multi-tty primitives that simply crash or cause Emacs to throw a signal. I think you discovered that while testing the latest changes in emacsclient. Or does my faulty memory fail me again? > If the Windows port defines the multi-tty feature, it just dilutes its > meaning. Is that not true for the DOS port? The DOS port supports only one kind of frame, so several different kinds are not an issue (again, assuming Lisp code without bugs mentioned above). When I worked on reviving the DOS port, I actively tried to break it by using multi-tty primitives, but any use-case that can be reproduced on DOS either worked or silently did nothing. That is why I didn't bother to revoke the multi-tty feature in the DOS port. If someone shows me a use-case that contradicts that, I will think again.