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#20675: 24.3; emacsclient cannot talk to emacs Date: Tue, 1 Oct 2019 20:05:49 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="199751"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 20675@debbugs.gnu.org To: Bruce Korb Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Oct 01 20:07:12 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 1iFMYI-000pky-6k for geb-bug-gnu-emacs@m.gmane.org; Tue, 01 Oct 2019 20:07:10 +0200 Original-Received: from localhost ([::1]:46344 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iFMYH-0000Kp-4O for geb-bug-gnu-emacs@m.gmane.org; Tue, 01 Oct 2019 14:07:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38834) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iFMYB-0000Kf-7X for bug-gnu-emacs@gnu.org; Tue, 01 Oct 2019 14:07:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iFMYA-0002As-4L for bug-gnu-emacs@gnu.org; Tue, 01 Oct 2019 14:07:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54132) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iFMYA-0002Am-1P for bug-gnu-emacs@gnu.org; Tue, 01 Oct 2019 14:07:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iFMY9-0001bw-Pl for bug-gnu-emacs@gnu.org; Tue, 01 Oct 2019 14:07:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Stefan Kangas Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 01 Oct 2019 18:07:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 20675 X-GNU-PR-Package: emacs Original-Received: via spool by 20675-submit@debbugs.gnu.org id=B20675.15699531746131 (code B ref 20675); Tue, 01 Oct 2019 18:07:01 +0000 Original-Received: (at 20675) by debbugs.gnu.org; 1 Oct 2019 18:06:14 +0000 Original-Received: from localhost ([127.0.0.1]:34720 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iFMXN-0001ao-VG for submit@debbugs.gnu.org; Tue, 01 Oct 2019 14:06:14 -0400 Original-Received: from mail-pl1-f175.google.com ([209.85.214.175]:39617) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iFMXI-0001aT-Bj for 20675@debbugs.gnu.org; Tue, 01 Oct 2019 14:06:12 -0400 Original-Received: by mail-pl1-f175.google.com with SMTP id s17so5873262plp.6 for <20675@debbugs.gnu.org>; Tue, 01 Oct 2019 11:06:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3s5lK65pUgs6NZAG7NPswAoLPxpmeokX+KnNbuMwVz0=; b=Ii8tkjysbnc3PAnymgr18xCnO78I02Wteb5fpEMX2/IkSfn1Sz2aMl/A3AJRR/Bgfv QXAfYeqK4YX/WsLjxsJkAVzbE53oj3Yl3CFdFF46Z7qNc895KyPOec2jubnB04/uuX0t CY70456t1ftWZSm4CL9FfZstRi4IU400gsd2NvgG4Urk6qkSfIRVj1NgVVOiPMF0ey2X 6SNJg9GmOTDyVK/oMdPbAEOpF8LZozE+r/hsyhtInQUEgKTnxT18giQ0CTkVCV6+qM5K kefdtaHAI78/EihLQUYKgbrbCAIX4tmoPqAaW0mRh/c9gyFz/+kAuNRHLqqN/yTZL/vz bsig== X-Gm-Message-State: APjAAAX9q+y9mlwxfxTgJUPcdxiNPMQfqlNuytxilw/1c2ZqwwIsMwd4 graX+UX4CYRtUEwVKHS97uvGdBzqCGLMNqVW8norYcr2 X-Google-Smtp-Source: APXvYqwig0WkhI6rPP2nkIFb/pM522YHw+JqkiPz769KxWgo7KsQKosf3FGQJp32MurYuFICwn5eoLmOg8BO82Vpct4= X-Received: by 2002:a17:902:a515:: with SMTP id s21mr28240374plq.259.1569953162299; Tue, 01 Oct 2019 11:06:02 -0700 (PDT) In-Reply-To: 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:168063 Archived-At: Bruce Korb writes: > > > The problem is that I need to redirect TMPDIR to different places for > > > different tasks. So that explainer above might get expanded to include > > > mention of the fact that this directory: ${TMPDIR}/emacs$(id -u) > > > is used for communication. I'd have found the problem long ago. > > > > > > So please consider this an RFE to the above "can't find socket" message. > > > > Are you saying that you are trying to use emacsclient with a different > > $TMPDIR than the one you used for the emacs server? > > What I am attempting to do is to have multiple (two) cscope-s running > each talking to a different server. The real issue being that I needed > emacs windows tied to a specific invocation of cscope. It seemed the > best way to do that was to have multiple servers running since "last > active emacs window" is inadequate. Anyway, for me, I retired 6 months > after posting this and doubt I'll ever want to run multiple cscopes in > parallel ever again. :) Thanks for reporting back, and I hope you're enjoying your retirement. If I understand correctly, the problem is that there is a mismatch between the $TMPDIR used on the emacs server and on the emacs client. I think that the answer in this case should be: don't change $TMPDIR unless you have to, and if you do, please be careful with how you do it. In other words, I have a hard time seeing how we could do better here. (I also note that we recently started preferring $XDG_RUNTIME_DIR if that's set.) But perhaps we could do something about the documentation. I see that server-socket-dir is documented in the Emacs FAQ, but not at all in the manual. Is that really right? I would have expected it to be the other way around: the FAQ is just the quick-start version, and one would have to read the manual for all the details. Best regards, Stefan Kangas