[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Questions about XDG_RUNTIME_DIR and server-socket-dir

From: Phil Sainty
Subject: Re: Questions about XDG_RUNTIME_DIR and server-socket-dir
Date: Sun, 3 Feb 2019 22:18:28 +1300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1

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

(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.)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]