From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: w32 does not have emacsclient/server Date: Tue, 09 Aug 2005 20:49:25 -0400 Message-ID: References: <42D75F2C.3040303@student.lu.se> <85zmso79mt.fsf@lola.goethe.zz> <42D7AA3E.7040508@student.lu.se> <42D7C92E.2020100@gnu.org> <42D7CDAA.4070400@student.lu.se> <85zmsorthl.fsf@lola.goethe.zz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1123635565 4622 80.91.229.2 (10 Aug 2005 00:59:25 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 10 Aug 2005 00:59:25 +0000 (UTC) Cc: Emacs Devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 10 02:59:22 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1E2evb-0001Qo-O4 for ged-emacs-devel@m.gmane.org; Wed, 10 Aug 2005 02:58:44 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E2eyh-0002uw-42 for ged-emacs-devel@m.gmane.org; Tue, 09 Aug 2005 21:01:55 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1E2evJ-0001m0-1y for emacs-devel@gnu.org; Tue, 09 Aug 2005 20:58:25 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1E2ev1-0001aV-TM for emacs-devel@gnu.org; Tue, 09 Aug 2005 20:58:21 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E2euw-0001Za-L3 for emacs-devel@gnu.org; Tue, 09 Aug 2005 20:58:02 -0400 Original-Received: from [195.186.19.66] (helo=mail22.bluewin.ch) by monty-python.gnu.org with esmtp (Exim 4.34) id 1E2f0e-0001u2-UQ for emacs-devel@gnu.org; Tue, 09 Aug 2005 21:03:57 -0400 Original-Received: from empanada.local (83.76.14.40) by mail22.bluewin.ch (Bluewin 7.2.063) id 42E684E0001FD99F; Wed, 10 Aug 2005 00:49:21 +0000 Original-Received: by empanada.local (Postfix, from userid 502) id D9CF05FFBC9; Tue, 9 Aug 2005 20:49:25 -0400 (EDT) Original-To: Juanma Barranquero In-Reply-To: (Juanma Barranquero's message of "Tue, 9 Aug 2005 02:19:45 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (darwin) 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:41832 >> I'd rather see "server-name" which could be a path to a unix socket (like >> now) or just a relative name of a unix socket (like now) or the name of >> a server to be found in ~/.emacs.servers. I.e. if there is no unix socket >> of that name, lookup ~/.emacs.servers for TCP servers. > Another thing: that would mean having to decide whether you're > creating an AF_UNIX or AF_INET server, My text above refers to the emacsclient case. For the server, of course you want the choice between Unix and TCP to be done explicitly via a configuration. > and if the former, connection from some non-Unix emacsclients (like > Windows) would be impossible. Is that a bug or a feature? If the socket is a Unix socket, connection is not possible remotely, so every client will necessarily be a (or rather THE) unix client. > I'm really not convinced than keeping both Unix sockets and TCP/IP > sockets is a good idea. I'm open to being convinced otherwise, though. The new TCP code is unlikely to be as problem free, so for the sake of ensuring that what used to work still works, I'd recommend you write your patch such that when the old code worked, it will work just as smoothly as before (i.e. use Unix sockets by default when available) and only when the old code didn't work use TCP sockets (which then won't be much worse than before unless you introduced a security hole). Stefan