From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Glenn Morris <rgm@gnu.org>
Cc: 35300@debbugs.gnu.org
Subject: bug#35300: 27.0.50; emacsclient on remote sessions no longer works
Date: Sat, 20 Apr 2019 19:59:27 +0200 [thread overview]
Message-ID: <874l6spngg.fsf@telefonica.net> (raw)
In-Reply-To: <bw5zr84lpm.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sat, 20 Apr 2019 13:42:45 -0400")
Glenn Morris <rgm@gnu.org> writes:
> *** emacsclient supports an EMACS_SOCKET_NAME environment variable.
> If set, it provides the default server socket filename.
> The command-line emacsclient option --socket-name overrides it.
>
> *** The Emacs server/client now use $XDG_RUNTIME_DIR/emacs for sockets,
> if the XDG_RUNTIME_DIR environment variable is defined.
> This is more secure than the old practice of using TMPDIR.
> If your client cannot find the server socket, check XDG_RUNTIME_DIR
> has the same value in both client and server environments.
> You can use the EMACS_SOCKET_NAME environment variable (see above)
> to specify a particular socket.
This is an improvement, yes. But I'll like to see even a stronger hint
on the output of emacsclient, once we agree that there is no better
solution than to use XDG_RUNTIME_DIR.
It is unfortunate that this change added more requirements to
emacsclient to work correctly.
next prev parent reply other threads:[~2019-04-20 17:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 21:21 bug#35300: 27.0.50; emacsclient on remote sessions no longer works Óscar Fuentes
2019-04-19 0:36 ` Glenn Morris
2019-04-19 1:54 ` Óscar Fuentes
2019-04-19 7:36 ` Eli Zaretskii
2019-04-19 12:36 ` Óscar Fuentes
2019-04-19 13:10 ` Eli Zaretskii
2019-04-19 13:31 ` Óscar Fuentes
2019-04-19 14:08 ` Eli Zaretskii
2019-04-19 14:30 ` Óscar Fuentes
2019-04-19 15:07 ` Eli Zaretskii
2019-04-19 15:40 ` Óscar Fuentes
2019-04-20 17:42 ` Glenn Morris
2019-04-20 17:59 ` Óscar Fuentes [this message]
2019-04-20 19:31 ` Paul Eggert
2019-04-20 19:52 ` Óscar Fuentes
2019-04-24 16:13 ` Glenn Morris
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=874l6spngg.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=35300@debbugs.gnu.org \
--cc=rgm@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).