From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Phil Sainty Newsgroups: gmane.emacs.devel Subject: Re: Questions about XDG_RUNTIME_DIR and server-socket-dir Date: Sun, 3 Feb 2019 22:18:28 +1300 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="226810"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 To: Eli Zaretskii , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Feb 03 10:19:14 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gqDvm-000wsd-3f for ged-emacs-devel@m.gmane.org; Sun, 03 Feb 2019 10:19:14 +0100 Original-Received: from localhost ([127.0.0.1]:53332 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gqDvk-0005tn-VL for ged-emacs-devel@m.gmane.org; Sun, 03 Feb 2019 04:19:12 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:33753) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gqDv9-0005ti-AF for emacs-devel@gnu.org; Sun, 03 Feb 2019 04:18:36 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gqDv8-0001I5-8d for emacs-devel@gnu.org; Sun, 03 Feb 2019 04:18:35 -0500 Original-Received: from smtp-4.orcon.net.nz ([60.234.4.59]:35374) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gqDv7-0001Bk-UA; Sun, 03 Feb 2019 04:18:34 -0500 Original-Received: from [150.107.172.32] (port=53600 helo=[192.168.20.103]) by smtp-4.orcon.net.nz with esmtpa (Exim 4.86_2) (envelope-from ) id 1gqDv2-0001dn-UU; Sun, 03 Feb 2019 22:18:29 +1300 In-Reply-To: Content-Language: en-GB X-GeoIP: NZ X-Spam_score: -2.9 X-Spam_score_int: -28 X-Spam_bar: -- X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 60.234.4.59 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:232926 Archived-At: On 3/02/19 7:01 PM, Eli Zaretskii wrote: > The value of server-name can include leading directories, so I think > you can already have what you want. Right? I don't see any current way of specifying the server-name via the environment when running emacs, though? For hopeful clarity, my requirement includes the situation where a user has an init file containing (server-start) (let's say that's all that it contains), and they run plain 'emacs' via the wrapper twice, and should end up with two separate emacs instances, each running its own server using a distinct non-conflicting socket. The wrapper doesn't know whether their init file will start a server; but if a server is started then it must not conflict with other Emacs servers (created with or without the wrapper). And if the user instead ran 'emacs --daemon=foo' via the wrapper twice, then again there should be two non-conflicting 'foo' sockets. Making the wrapper control TMPDIR achieves all this for previous versions. (If they ran 'emacs --daemon=/path/to/foo' twice then it's fine for that to conflict. It's just the default server-socket-dir that I'm wanting to have environmental influence over.) -Phil