From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.bugs Subject: bug#13319: 24.2.91; emacsclient doesn't find server with nonstandard name Date: Fri, 16 Jul 2021 03:08:04 +0200 Message-ID: <87y2a7nk0b.fsf@web.de> References: <87zk0u405l.fsf@web.de> <8738ym3ren.fsf@web.de> <87czrjina4.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10621"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Andreas Schwab , 13319@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jul 16 03:09:21 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m4CLx-0002WN-80 for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 16 Jul 2021 03:09:21 +0200 Original-Received: from localhost ([::1]:43532 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m4CLv-0008OX-IC for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 15 Jul 2021 21:09:19 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40528) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m4CLe-0008OI-2s for bug-gnu-emacs@gnu.org; Thu, 15 Jul 2021 21:09:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:38555) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1m4CLd-00013S-QD for bug-gnu-emacs@gnu.org; Thu, 15 Jul 2021 21:09:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1m4CLd-00039v-JU for bug-gnu-emacs@gnu.org; Thu, 15 Jul 2021 21:09:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Michael Heerdegen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 16 Jul 2021 01:09:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 13319 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 13319-submit@debbugs.gnu.org id=B13319.162639769812096 (code B ref 13319); Fri, 16 Jul 2021 01:09:01 +0000 Original-Received: (at 13319) by debbugs.gnu.org; 16 Jul 2021 01:08:18 +0000 Original-Received: from localhost ([127.0.0.1]:50101 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1m4CKv-000392-Sn for submit@debbugs.gnu.org; Thu, 15 Jul 2021 21:08:18 -0400 Original-Received: from mout.web.de ([217.72.192.78]:53213) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1m4CKr-00038l-JW for 13319@debbugs.gnu.org; Thu, 15 Jul 2021 21:08:16 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1626397685; bh=nRf+A+6QO7CEAYLbyYm7vnh77rSAjE0/8uaQfNDZlWA=; h=X-UI-Sender-Class:From:To:Cc:Subject:References:Date:In-Reply-To; b=H6PIbdz59zu5vglvd/OHvKnTcPD4YEmUV2h0v0UbrOh5gkhK9Ebd7YO0wrC08EV21 HJyf0f4JQLnksNRfJmUYE3jJ0/YMi7Bayljn13YwIDPOAP4BGwu86KkCqI203H0JMv LR7iYjfoydJLfJZ4iO+qCuMP9I9odg5wXDhynyoQ= X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9 Original-Received: from drachen.dragon ([88.66.201.45]) by smtp.web.de (mrweb102 [213.165.67.124]) with ESMTPSA (Nemesis) id 0MWRzK-1lc5SJ2mz4-00XeUo; Fri, 16 Jul 2021 03:08:05 +0200 In-Reply-To: <87czrjina4.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 15 Jul 2021 17:56:19 +0200") X-Provags-ID: V03:K1:gT2JZRw2P6ubQegl/3VdaAq+FuM1oW55A0vizx1bIU/GYrSpQ2B f2DCrC7RpDeFMboTmlqtVLUQ4DEKhUNyZu+i4RX6VIyAh1hrQBRuKOcC3ofoHayQEdPxcp2 bhYQMhcshbTZs1PC58QsG2ytD6zB7Tf9iKPZFVc+d76MdLZxDZaCiFsmHBrDGLu2Yb3a95/ NmV07hY0hha+IyT3tjOhQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:O/2ZpRw6H98=:e3Rfqp1DOE86WZ+Fy1XvN4 uXKHj7/GoIkGK89Ejim3190+7RrbWslUAYg3s7Ey80CQu8M+n9w1XroFkNLiR/Phgvsr6R624 bDvYzWfS6ccB+CWOzTrVu91AaBYxJaJCvJz9jL4Uc/6en2hJFfr8fhXHFS9yu00xKylt06OOn GGUhTHqoU3Z+LGOlK1+NnsX1ayFkIwuUls4qkfWUuR1eBFkmg4DKzlJ3nnfQLPpbmbO4Fof+O LN0eW5mwhsJb9pz8ydKek+JWNfNoqWXaTvDnCVdO1LQIYYS508ekmRWldP6IgH8mJtWW7Fibx jgnu41j+Sr8lnsh11tRScVNKpfq2wMln4YII2UUddSLZzaDIYyGZ4bnUTuBonSBhGq+5TYAk/ FakRKclrTFVORTmZnN60XRSVDigQlwr+M9NhMsbUlcudhNxjgRM89Nc01o49yPJrZAMEr5k8s pf4TBF37gG6C1YVTnjz4GVgn/NNK+SZMFgoPe5e7tqIBRRPhfvECtrA8n8Yf4+B3ZMJkK+9ma g+hLP3YKpzc0BoooJH60U9cQMORw4pZKcmYwgyhwylgL5fZWGLaC81fMDIQQYvhY+jeAegq/q BWtEt/bCOahGjH6L8ELFAbENHTF8HNmQJSo8fGW+ivrsrpx8Ex/HykGhDhSowHGbJn/2FpIMa /+0xemCiQk7ZsRxNhUSZMLxN1P2pzdZQpOfTjWLvIWP/XargGqh3I0GFwgm+KS3Ecb95ZYqps DcBmwtaIrlkgkrYIjA6O1qGx2KALBPYcBGrQMXBuAIjdS1c+HUKBp/2eC4LF7W4tzF60DGoa X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:210063 Archived-At: Lars Ingebrigtsen writes: > >> This is questionable. How does it know that a random socket is a emacs > >> server socket? > > > > Here on Debian, it looks under /tmp/emacs$UID. Can there be any other > > socket? > > This was eight years ago, and some things have changed in this area > (like the location of the server socket), but the issue still remains, I > think? Seems so. > That is, the client won't look around for a socket with a > non-standard name. > > But I tend to think that this is actually the correct behaviour -- > having emacsclient guess at what socket name to use sounds a bit too > DWIM to me: I may deliberately have set up a server to do one very > specific thing under a non-standard name, and I would not want any > random emacsclient invocation to use that special server just because it > can't find the standard socket. (Which I may just have forgotten to > start the server for.) What would happen in this case? Can't you use another place to store the socket then? > So I think this behaves as it should. Anybody else got another opinion? I don't know if something like you describe could be prevented. If you are sure that my suggestion would cause trouble, then I'm ok with closing. I'm too ignorant about how this socket stuff is working to have an opinion. Michael.