unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: Questions about XDG_RUNTIME_DIR and server-socket-dir
Date: Mon, 04 Feb 2019 05:30:24 +0200	[thread overview]
Message-ID: <83k1igut67.fsf@gnu.org> (raw)
In-Reply-To: <e966d2eb8265cbda81f9603f86add371@webmail.orcon.net.nz> (message from Phil Sainty on Mon, 04 Feb 2019 10:12:50 +1300)

> Date: Mon, 04 Feb 2019 10:12:50 +1300
> From: Phil Sainty <psainty@orcon.net.nz>
> Cc: emacs-devel@gnu.org
> 
> On 2019-02-04 00:21, Eli Zaretskii wrote:
> > The client already heeds to EMACS_SOCKET_NAME.  As for the server,
> > since Emacs is invoked via a wrapper, I presume the wrapper could set
> > server-name from the same environment variable, via --eval, no?
> 
> No, --eval isn't processed until after the init file is processed,
> so if the user called (server-start) in their init file then the socket
> is already set.

You can always restart the server with another --eval, right?

> My recollection is that I couldn't find any way of doing something
> like that.

Only because yours is a very convoluted arrangement, not typical of
"normal" usage.  Defcustoms are supposed to be customized from init
files, not controlled by environment variables from outside of Emacs.

> (I do still think a EMACS_SOCKET_DIR environment variable would be a
> beneficial addition, as the current code doesn't facilitate this.)

We don't need a variable to set a directory when we already have one
for setting the file name, which could include leading directories.



  reply	other threads:[~2019-02-04  3:30 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
2019-02-03 11:21     ` Eli Zaretskii
2019-02-03 21:12       ` Phil Sainty
2019-02-04  3:30         ` Eli Zaretskii [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83k1igut67.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=psainty@orcon.net.nz \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).