From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.bugs Subject: bug#23202: 24.5; emacsclient confusing server connection message Date: Wed, 06 Nov 2019 01:45:37 +0100 Message-ID: <87lfst6de6.fsf@marxist.se> References: <87h9fjzl0d.fsf@aol.com> <874l35aitz.fsf@mouse.gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="224000"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: 23202-done@debbugs.gnu.org, Live System User To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Nov 06 01:50:55 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iS9XC-000w0u-LF for geb-bug-gnu-emacs@m.gmane.org; Wed, 06 Nov 2019 01:50:54 +0100 Original-Received: from localhost ([::1]:52022 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iS9Sh-0002fv-Hr for geb-bug-gnu-emacs@m.gmane.org; Tue, 05 Nov 2019 19:46:15 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47887) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iS9SX-0002fU-5g for bug-gnu-emacs@gnu.org; Tue, 05 Nov 2019 19:46:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iS9SV-0005Qw-Q4 for bug-gnu-emacs@gnu.org; Tue, 05 Nov 2019 19:46:05 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:58681) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iS9SV-0005QQ-JI for bug-gnu-emacs@gnu.org; Tue, 05 Nov 2019 19:46:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iS9SU-0004bz-Rd for bug-gnu-emacs@gnu.org; Tue, 05 Nov 2019 19:46:03 -0500 Resent-From: Stefan Kangas Original-Sender: "Debbugs-submit" Resent-To: bug-gnu-emacs@gnu.org Resent-Date: Wed, 06 Nov 2019 00:46:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: cc-closed 23202 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: unreproducible Mail-Followup-To: 23202@debbugs.gnu.org, stefan@marxist.se, nyc4bos@aol.com Original-Received: via spool by 23202-done@debbugs.gnu.org id=D23202.157300114916908 (code D ref 23202); Wed, 06 Nov 2019 00:46:02 +0000 Original-Received: (at 23202-done) by debbugs.gnu.org; 6 Nov 2019 00:45:49 +0000 Original-Received: from localhost ([127.0.0.1]:39267 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iS9SH-0004OF-Aw for submit@debbugs.gnu.org; Tue, 05 Nov 2019 19:45:49 -0500 Original-Received: from host.gofardesign.uk ([208.79.239.190]:42831) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iS9SE-0004Gy-MA for 23202-done@debbugs.gnu.org; Tue, 05 Nov 2019 19:45:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=marxist.se; s=default; h=Content-Type:MIME-Version:Message-ID:Date:References: In-Reply-To:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=0TruAfIJqOo2oH98FxpMeqT+XryEBbnuOcp61rBmLm8=; b=O9BqtiFJB6TiAua8tK6/PB/0sv WIaj+mje0vawv2+W+suth1SGheAWYXr2jiyH8wYIfJAUljA8HllV3asCSmGQ5RsytmrV6JNKm6FZk koZFNL1rO4anmXzGSc4hnOIWBsrLmDVSOPSV7pHu8nqoDRlqqcJkcKWC54hv4aF/uZZA=; Original-Received: from h-70-69.a785.priv.bahnhof.se ([155.4.70.69]:45262 helo=localhost) by host.gofardesign.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from ) id 1iS9S7-0006Rg-TU; Tue, 05 Nov 2019 18:45:40 -0600 In-Reply-To: <874l35aitz.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Mon, 29 Jul 2019 00:35:20 +0200") X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.gofardesign.uk X-AntiAbuse: Original Domain - debbugs.gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - marxist.se X-Get-Message-Sender-Via: host.gofardesign.uk: authenticated_id: stefan@marxist.se X-Authenticated-Sender: host.gofardesign.uk: stefan@marxist.se X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:171001 Archived-At: Lars Ingebrigtsen writes: > Live System User writes: > >> Now, when invoking emacsclient, I get the following message: >> >> $ emacsclient +12:2 ~/.emacs >> emacsclient: can't find socket; have you started the server? >> To start the server in Emacs, type "M-x server-start". >> Waiting for Emacs... >> >> >> Even though I get this message, apparently. emacsclient does find the >> network socket and brings up the "~/.emacs" file in an emacs window. >> >> In Emacs, invoking `(list-processes)' yields: >> >> server listen -- -- (network server on local) >> server <127.... open -- -- (network connection to 127.0.0.1) >> >> >> .% *Process List* 166 Process Menu >> * .emacs 73761 Emacs-Lisp ~/.emacs >> % *GNU Emacs* 858 Fundamental >> *scratch* 191 Lisp Interaction >> %* *Messages* 2285 Messages >> >> >> So why give a warning message of "can't find socket" if the connection is >> subsequentially successful (the server *was* started) and it gets its >> connection information from the server file, even though the server file >> is not an actual "socket"? >> >> Could it be that invoking emacsclient, by default, first looks for the >> server socket file in /tmp/emacs/server ? And then falls back to >> the ~/.emacs.d/server/server server file if that socket doesn't >> exists? >> >> But because of the default precedence. it doesn't determine whether a >> server actually doesn't exists before emitting the warning? > > (I'm going through old Emacs bug reports that haven't received any > response.) > > I'm unable to reproduce this in Emacs 27. Are you still seeing this > behaviour? I'm also unable to reproduce this on Emacs 27. Since more information was requested, but none was given within 14 weeks, I'm now closing this bug as unreproducible. If anyone can reproduce this, please report back and/or reopen the bug report. Best regards, Stefan Kangas