From: Phil Sainty <psainty@orcon.net.nz>
To: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Questions about XDG_RUNTIME_DIR and server-socket-dir
Date: Sun, 3 Feb 2019 22:18:28 +1300 [thread overview]
Message-ID: <e5b8cd75-ddd2-8663-2277-2ca5f852a2cd@orcon.net.nz> (raw)
In-Reply-To: <BD04A93A-9A41-4CC6-A68D-DB25C506EA35@gnu.org>
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
next prev parent reply other threads:[~2019-02-03 9:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 5:21 Questions about XDG_RUNTIME_DIR and server-socket-dir Phil Sainty
2019-02-03 6:01 ` Eli Zaretskii
2019-02-03 9:18 ` Phil Sainty [this message]
2019-02-03 11:21 ` Eli Zaretskii
2019-02-03 21:12 ` Phil Sainty
2019-02-04 3:30 ` Eli Zaretskii
2019-02-04 4:10 ` Stefan Monnier
2019-02-04 5:06 ` Phil Sainty
2019-02-03 6:10 ` Paul Eggert
2019-02-03 8:41 ` Phil Sainty
2019-02-03 16:42 ` Paul Eggert
2019-02-04 12:49 ` Ulrich Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5b8cd75-ddd2-8663-2277-2ca5f852a2cd@orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.