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

On 2019-02-04 16:30, Eli Zaretskii wrote:
> You can always restart the server with another --eval, right?

I think that would be closing the stable door after the horse has
bolted, if the default socket had potentially been clobbered in
the interim :)


> Only because yours is a very convoluted arrangement, not typical
> of "normal" usage.

Oh absolutely.  (Although I believe others will find the script useful
as well once I've released it more generally, so it might become at
least slightly less abnormal.)


> Defcustoms are supposed to be customized from init
> files, not controlled by environment variables from outside of Emacs.

It's only the fact that separate instances can conflict with one
another's sockets which makes me want this, because that's rather an
awkward issue which (in my convoluted arrangement) isn't reliably
addressed by init files simply because I'm not imposing any particular
requirements on init files (and users might run 'emacs -q' in any
case).  Enforcing the separation of server instances really needs some
kind of external support.


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

I can only reiterate that this doesn't cover my particular use-case;
but that's ok, as it seems that setting XDG_RUNTIME_DIR will be a
workaround for that.  If I find that I need to revisit this question,
I'll provide more context.

Shall I raise a bug report for the fact that emacs ignores that existing
(EMACS_SOCKET_NAME) environment variable?


-Phil




  parent reply	other threads:[~2019-02-04  5:06 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
2019-02-04  4:10           ` Stefan Monnier
2019-02-04  5:06           ` Phil Sainty [this message]
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=b8aba4fa0f46473a7326f03870860da3@webmail.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 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).